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.
Squash+Merge title = PR title doesn't handle updated PR titles
See original GitHub issueFeature #276, Force "squash and merge" title to be the pull request title, doesn’t take into account that a user might update the PR title before using the squash+merge button. They have to reload the page first to get the new PR title into the input field, which is unexpected.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:13 (8 by maintainers)
Top Results From Across the Web
Squash+Merge title = PR title doesn't handle updated PR titles
I opened a PR in two windows, changed the PR title in window two, saw the title update in the first, and hit...
Read more >Default to PR titles for squash merge commit messages
You can now default to using PR titles for all squash merge commit messages. Navigate to 'Settings' in your repository and scroll down...
Read more >Allow editing of the full commit message when merging a pull ...
This does not appear to work for a Squash merge where there are multiple commits to squash. The log message in git is...
Read more >Merge strategies and squash merge - Azure Repos
Squash merge commit doesn't have a reference to the topic branch, it will produce a new commit, that contains all changes from the...
Read more >Squash commits considered harmful - DEV Community
Over time I've learned the value of a squash merge. If a PR is too big to be able to describe in one...
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
I’ve been seeing this issue for some time too, just forgot to open an issue.
Closing in favor of https://github.com/sindresorhus/refined-github/issues/1790