[FR] Merge commit message template

Bitbucket Cloud has the corresponding feature request: Issue #14101. It seems that it won’t be implemented any time soon.

With Bitbucket Cloud now supporting Squash merge strategy for PRs, the commit message becomes really important (vs having some generated commit message for merge commits). I believe for many teams it would make more sense for Squash to put PR title as a first line, instead of default Bitbucket’s suggestion Merged in ${PR_SOURCE_BRANCH} (pull request #${PR_NUMBER}).

refined-bitbucket can support simple text configuration for a template where users can use ${PR_TITLE}, ${PR_SOURCE_BRANCH}, ${PR_TARGET_BRANCH}, ${PR_NUMBER}, ${APPROVED_BY_LIST} variables to inline the corresponding data to generate a commit message for merging the PR.

[reyronald]

Hey everyone, this feature is included in version 3.13.0. Please try it out and let me know what you think and if you find any issues with it.

[deepakrb]

Nice to be back @reyronald 😄

I was fully on board with @ikornienko’s suggestions, as in a system similar to the current Pull Request template system where you can commit a Merge Message markdown file (with variable injection) to the root directory of the project which would be inserted into the merge message.

Just speaking personally, we have a policy where we currently manually remove the first “Merged in …” comment for squashes because it really has no use to us. It makes logging and reverting commits much more difficult when someone forgets to do it and we can’t easily read the feature merge.

Taking it one step further we could also possible make those variable available in the pull request template, what do you think?