SemanticCommitType setting is ignored

[nosajsnikta]

I am trying to get renovate to use semantic commits so that any PRs raised will be prefixed with 'fix(deps):'

The only way I am currently able to do this is using the following config setting in my renovate.json file:

"commitMessagePrefix": "fix(deps):"

This seems like a bodge, as I think the following is more suitable:

semanticCommitType: "fix"

however, this always prefixes with 'chore(deps):' implying that the setting is being ignored. I don't believe I need to enable semanticCommits as the default of 'auto' should be sufficient.

Can anyone point me in the right direction? I'm using renovate version 22.25.0 if that helps

[rarkins]

If you're extending config:base then it includes this preset setting semantic prefixes: https://docs.renovatebot.com/presets-default/#semanticprefixfixdepschoreothers

Try adding ":semanticCommitTypeAll(fix)" to your extends array to override it.

[nosajsnikta]

Thanks for your reply My config.js does extend config:base so I can try what you said. Out of interest is it possible to have an 'extends' in config.js and then a further 'extends' in the project renovate.json? I did notice that the docs said you cannot define your extends array in a config.js also so if you can advise there that would be great. Thanks

…

On Wed, 27 Jan 2021, 21:22 Rhys Arkins, ***@***.***> wrote: If you're extending config:base then it includes this preset setting semantic prefixes: https://docs.renovatebot.com/presets-default/#semanticprefixfixdepschoreothers Try adding ":semanticCommitTypeAll(fix)" to your extends array to override it. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8440 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQY2SSCZYIMMM7KQT54QDX3S4B723ANCNFSM4WVZU44Q> .

[rarkins]

You can have both. We do support extends in config.js now but recommend they're instead in the repo config.

[nosajsnikta]

Ok thanks for the tips all working well now. Thanks

…

On Wed, 27 Jan 2021, 21:49 Rhys Arkins, ***@***.***> wrote: You can have both. We do support extends in config.js now but recommend they're instead in the repo config. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#8440 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQY2SSAKQ3T6D6W53GPLEBLS4CC6RANCNFSM4WVZU44Q> .