https://github.com/ext/renovate-commit-message
https://github.com/ext/renovate-commit-message
Last synced: over 1 year ago
JSON representation
- Host: GitHub
- URL: https://github.com/ext/renovate-commit-message
- Owner: ext
- Created: 2022-09-10T14:32:49.000Z (almost 4 years ago)
- Default Branch: main
- Last Pushed: 2025-02-23T19:10:31.000Z (over 1 year ago)
- Last Synced: 2025-02-23T20:22:08.894Z (over 1 year ago)
- Size: 90.8 KB
- Stars: 0
- Watchers: 2
- Forks: 0
- Open Issues: 7
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Renovate commit messages for groups
Changing commit message for a package group does not seem to have any effect.
To reproduce this, this repo has a dependency to Jest 28 as well as some related packages all belongning to the group "jest monorepo".
As Jest 29 is released I expect a pull request for the group to upgrade v28 -> v29.
As an attempt to configure this the repo sets both the deprecated `commitMessage` and the individual action, prefix, suffix, topic and extra parts as part of a `packageRules`:
```json
{
"commitMessage": "commit message",
"commitMessageAction": "action",
"commitMessagePrefix": "prefix",
"commitMessageSuffix": "suffix",
"commitMessageTopic": "topic",
"commitMessageExtra": "extra"
}
```
## Expected behaviour
A PR with a commit message other than `"chore(deps): update jest monorepo"`.
Since `commitMessage` is set to literal `"commit message"` I would expect the commit message to be `"commit message"`.
If I remove `commitMessage` and rely on non-deprecated configuration I would expect the commit message to be `"prefix action topic extra suffix"`.
## Actual behaviour
Commit message is always `"chore(deps): update jest monorepo"`.