Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
[Question] Separate upgrade commits in a single PR #520
Which Renovate are you using?
Renovate Open Source CLI (using the docker image
Which platform are you using?
Have you checked the logs? Don't forget to include them if relevant
What would you like to do?
I've set the following package rule to be able to group all upgrades so that renovate bot will create a single branch and a single PR for upgrades.
But I also want to have separate commits instead of single
I've check configuration options but couldn't see any options for separate commits. I wonder if it's possible in renovate. Thanks in advance.
We're unlikely to support multiple commits per branch any time soon. Having a single commit makes a lot of our logic much simpler. It would take significant development to do, probably significant time to maintain forever and make sure we never break, and not actually achieve any functionality benefit.
My concern is more related to git history. For instance, if I merge this PR as is, it's hard to tell what is upgraded.
Currently, we do upgrade our dependencies with the help of maven version plugin but preparing the commit message, gathering the changelog, etc. are mostly manual.
For example, a couple of upgrade commits (which I am trying to achieve using renovate) from our codebase looks like the following:
Something I have been considering is to list all the upgrades within Renovate's commit messages. For example maybe it could be a markdown table. So if you have the commit message as "Update all dependencies" then the body of the commit message would then list everything that was committed.
Note that this would only be preserved in your master branch if you use either rebase or merge commits. If you squash commit then it's going to use the PR's content (I think).