BitBucket Better PR Commit Message
2 ratings
)Overview
This extension replaces BitBucket's default pull request commit message with a more useful message, especially if you squash PRs.
If your development workflow involves creating a pull request for every change, and you squash your PRs with the default commit message when you merge them, then your commit history has a bunch of entries that all look like "Merged in my-terse-branch-name (pull request #123)". These aren't especially helpful commit messages and "Merged in" just becomes noise. This extension will use the title of your PR as the commit message instead which should lead to a much more useful commit history. The bulleted list of individual commit messages and approvals will still appear in the body of the commit message. To tell Atlassian that this should be the default behavior, go to the following URL and vote for the issue. https://jira.atlassian.com/browse/BCLOUD-19402
5 out of 52 ratings
Google doesn't verify reviews. Learn more about results and reviews.
Reda BendiarJul 2, 2022
Bitbucket has many annoying parts in this is one of them. Can't wait for the company to move to github or other solutions. Meanwhile this extension is the way to go! Thank you.
VladJan 27, 2021
Very useful while BitBucket team can't update this for 9 years 😅 https://jira.atlassian.com/browse/BSERV-2894
Details
- Version1.1.3
- UpdatedJanuary 24, 2023
- Offered bySean Dwyer
- Size5.87KiB
- LanguagesEnglish
- Developer
Email
sean.dwyer+googlewebstore@gmail.com - Non-traderThis developer has not identified itself as a trader. For consumers in the European Union, please note that consumer rights do not apply to contracts between you and this developer.
Privacy
This developer declares that your data is
- Not being sold to third parties, outside of the approved use cases
- Not being used or transferred for purposes that are unrelated to the item's core functionality
- Not being used or transferred to determine creditworthiness or for lending purposes
Support
For help with questions, suggestions, or problems, visit the developer's support site