Customization of backported commit message
See original GitHub issueWould it be possible to customize the message of the cherry-picked commits?
Instead of Backport of ...
in the body, I’d like to copy the original commit description, adding a trailing:
(cherry picked from commit xxxxx)
.
See https://github.com/elastic/elasticsearch/commit/443d30888edc2e9fe71700eebf79dcf3814b0f01 as an example.
Would it be possible to expose the original commit message and sha as variables to be used inside the description?
Thanks,
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (4 by maintainers)
Top Results From Across the Web
How do I backport a commit in git? - Stack Overflow
Rebase essentially rolls back all your changes on the current branch to the fork (or last rebase), copies over newer changes and then...
Read more >Backports - OpenJDK Wiki
A. (often abbreviated to just. ) is a replica of an existing commit applied to a different repository. In most cases the backport...
Read more >Allow to customize automatic backports · Issue #37 - GitHub
@renatocaval you can now specify the commit message from the body https://doc.mergify.io/actions.html#defining-the-commit-message or from the PR ...
Read more >Backporting a change to a release branch - CockroachDB
Check the release notes in the commit messages, to ensure they are applicable to the branch (if a release note refers to another...
Read more >Backporting - ownCloud Documentation
If the maintainer agrees, create a new branch based on the respective stable branch, cherry-pick the needed commits to that branch and create...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Good idea. I’ll look into this!
I don’t think that’s a problem. According to the docs Github will use the the commit message (and not the PR body) if there’s only a single commit. If there are multiple commits the PR title, and the list of commit messages will be used. So in both cases the “cherrypick reference” will always be included