Commit messages changed format randomly

[naftis]

What would you like help with?

I think I found a bug

How are you running Renovate?

Mend Renovate hosted app on github.com

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

Randomly, our repository's all renovate PR's changed their title and commit messages: opencrvs/opencrvs-core#7086

This is our renovate configuration: https://github.com/opencrvs/opencrvs-core/blob/develop/renovate.json

Why would that happen all of a sudden?

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[rarkins]

Renovate docs, Semantic Commits

[naftis]

We're extending from "config:recommended":

If you extend from config:recommended then Renovate uses the chore prefix for nearly all updates.

Also it's odd that it randomly just changed without changing configuration

[rarkins]

It's not random. Read the first sentence in that link

[HonkingGoose]

I'll explain this in a bit more detail for you. 😉

Renovate saw the chore: check a record is already assigned commit message 2 days ago:

• opencrvs/opencrvs-core@d97656d

Renovate afterwards assumes your project is using Semantic Commits. Relevant quote from the docs: ¹

Renovate looks at the last 10 commit messages in the base branch to decide if the repository uses semantic commits.
If there are semantic commits, Renovate uses the conventional-commits-detector to decide what convention the commit messages follow.

How to disable Semantic Commits style PR from Renovate

If you do not want Renovate to automatically guess what commit style you want, put this in your repository's renovate.json config file:

{
  "extends": [":semanticCommitsDisabled"]
}

See this PR on your repository:

• chore: force Renovate to use Semantic Commits opencrvs/opencrvs-core#7176

Footnotes

1. Renovate docs, Semantic Commits ↩

[naftis]

Thank you! I should then explicitly enable them. I might not have been clear but we had semantic commits before and that's the style we want to continue as well. I got confused as to why it changed recently, but we will give the different config settings a try