Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Enable the extension to set merge commit title and message PR
See original GitHub issueIn Merge commit workflow it would be great to replace generic github behavior with the following, more sensible one:
Merge commit title:
PR title (#PR ID) (follows the existing fix-squash-and-merge-title feature convention)
Merge commit message:
PR description (top comment in a PR)
BTW, I already have a working code, can check in.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:5
- Comments:13 (9 by maintainers)
Top Results From Across the Web
Enable the extension to set merge commit title and message PR
In my view the default merge commit title and message are not useful. Assuming a developer enters relevant PR title and PR description,...
Read more >Default to PR titles for squash merge commit messages
Navigate to 'Settings' in your repository and scroll down to the Pull Requests section. Select Allow squash merging and then select Default to...
Read more >Change default title for pull request commits to not include PR id
Conventional commit requires the title to start with feat:, fix: etc., which is not the case with the current default message "Merged PR...
Read more >how can I customize git's merge commit message?
For a real solution one would have to extend a git command named 'fmt-merge-msg' that generates the oneline descriptions when passing the --log...
Read more >Commit message templates - GitLab Docs
Configure commit templates · On the top bar, select Main menu > Projects and find your project. · On the left sidebar, select...
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
@alex-111-gh Closing based on the discussion and lack of endorsement from maintainers. Refined GitHub would always stay an opinionated project of course, but please don’t let not merging that functionality stopping you from contributing other awesome features!
@alex-111-gh I actually like that you can differentiate merge commits from GitHub’s commit message. Also, this would create inconsistency as the commit message would be the new one only for people using the extension, not for anyone else.