Renovate: Customizable prefixes for upgrade commits and pin dependencies commits

Created on 6 Aug 2018  路  3Comments  路  Source: renovatebot/renovate

What would you like Renovate to be able to do?
Recently I've adapted the use of emojis for commit prefixes. Hence I'd like to use :arrow_up: as a "generic" commit prefix for renovate upgrade commits but also :pushpin: for those that pin dependencies in particular therefore I'd like to have configuration options for both cases with custom prefixes.

Describe the solution you'd like
Seing a similar idea that was proposed in https://github.com/renovatebot/renovate/issues/1867 I'd like to see a pinDependenciesCommitMessagePrefix (definitely need a better name) in addition to the commitMessagePrefix which would allow me to define both of my prefixes.

Describe alternatives you've considered
An alternative may be an option to enable "standard" emojis described here as prefixes. This approach would not allow customization though.

Most helpful comment

Ultimately I ended up without using semanticCommitType and only used pin to rewrite my default prefix. I skipped onboarding with my custom renovate.json already in the repo:

{
    "extends": [
        "config:base"
    ],
    "commitMessagePrefix": ":arrow_up:",
    "pin": {
        "commitMessagePrefix": ":pushpin:"
    },
    "rangeStrategy": "pin"
}

Of course this setup assumes that renovate doesn't do any other types of commits, otherwise 猬嗭笍 wouldn't make too much sense. Anyways, if someone stumbles upon this use case, just refer to my config.

All 3 comments

Hi, this should already be possible today via regular configuration using a combination of semanticCommitType and pin. If any questions on that configuration please raise an issue in the config-help repo describing what you've tried and what failed, etc.

A PR would also be welcome here if you think any documents would be improved by describing how to do this for others. Thanks

Thank you for pointing me to these configuration options. It seems I haven't understood what they were useful for in the first place.

Ultimately I ended up without using semanticCommitType and only used pin to rewrite my default prefix. I skipped onboarding with my custom renovate.json already in the repo:

{
    "extends": [
        "config:base"
    ],
    "commitMessagePrefix": ":arrow_up:",
    "pin": {
        "commitMessagePrefix": ":pushpin:"
    },
    "rangeStrategy": "pin"
}

Of course this setup assumes that renovate doesn't do any other types of commits, otherwise 猬嗭笍 wouldn't make too much sense. Anyways, if someone stumbles upon this use case, just refer to my config.

Was this page helpful?
0 / 5 - 0 ratings