Extended config with :semanticPrefixFix creates chore commit

[jdbruijn]

I've got my default configuration on GitHub. The configuration in vidavidorra/repo-template extends that configuration as shown below. Today PR #185 was created that used a chore commit type.

{
  "$schema": "https://docs.renovatebot.com/renovate-schema.json",
  "extends": ["github>vidavidorra/.github", ":semanticPrefixFix"]
}

Is this a bug or is my configuration wrong? I'd expected :semanticPrefixFix to set the commit type to fix, but do I need to use :semanticCommitTypeAll instead or something? If so, can someone please tell me what the difference between those two is?

[rarkins]

Using :semanticPrefixFix would work if it weren't for the fact that you're extending config:base which includes :semanticPrefixFixDepsChoreOthers.

So you could:

• Use :semanticCommitTypeAll instead
• Add :semanticPrefixFixDepsChoreOthers to ignorePresets
• Instead of extending config:base, remove it and add only the presets it contains that you want

[jdbruijn]

Thanks for the quick reply, I'll try that and mark as answer if it indeed works.

My understanding with the config, not sure where I got this from, was that the last config would overwrite the previous ones. Is that wrong then?

[jdbruijn]

• Add :semanticPrefixFixDepsChoreOthers to ignorePresets

Worked a treat (proof), thanks again!

[rarkins]

My understanding with the config, not sure where I got this from, was that the last config would overwrite the previous ones. Is that wrong then?

packageRules are executed in order, after base config. So because the one you were trying to override was a package rule, it was executed after. It's not perfect/intentional - we're trying to work out a better/more predictable way for a future breaking release.