-
Suggestion
-
Resolution: Done
From BCLOUD-11571:
Prior to activating the templates, I could use a commit message like the following:
Derezz the master control program
MCP turned out to be evil and had become intent on world domination.
This commit throws Tron's disc into MCP (causing its deresolution)
and turns it back into a chess game.
And it would use the first line (subject line) as the PR title and the message would automatically be inserted into the description. If I've already written a detailed commit message, I don't want to have to re-type it for the PR.
Latest update from Atlassian 2023-07-20
We have added a capability that lets you substitute a list of commit messages by using the variable {{commit_messages}} in a default pull request description template. Docs are here: https://support.atlassian.com/bitbucket-cloud/docs/pull-request-and-merge-settings/
- is duplicated by
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[BCLOUD-17743] Support commit list substitution in pull request description templates
Hi all, good news from the Bitbucket team:
We have added a capability that lets you substitute a list of commit messages by using the variable {{commit_messages}} in a default pull request description template. Docs are here: https://support.atlassian.com/bitbucket-cloud/docs/pull-request-and-merge-settings/
All comments
Hi all, good news from the Bitbucket team:
We have added a capability that lets you substitute a list of commit messages by using the variable {{commit_messages}} in a default pull request description template. Docs are here: https://support.atlassian.com/bitbucket-cloud/docs/pull-request-and-merge-settings/
Hi all, it's Dave from the Bitbucket PM team. Just a quick update that we are actively working on this. I'll update you here when we release the feature!
Really? It's been almost 4 years and this issue is still unresolved. We need these features as Bernd mentioned:
> Please add the following parameters to be used in a pull request merge template:
- source branch
- target branch
- a short list of included commit messages (first line only)
- an extended list of include commit messages (full commit messages)
- optionally include author/committer, date of each included commit
This feature was added but not well done... see my comment here: https://community.atlassian.com/t5/Bitbucket-discussions/Save-time-with-default-pull-request-descriptions/td-p/971663#M3707
This would be so nice! Gitlab has this feature. Github has this feature. Bitbucket, please add this feature!
How long will you guys take to develop this simple feature. We need this!
Seems like such a basic feature it almost seems like an oversite. And such a simple feature takes 3 years to implement?
@Martin Edwards - That's the point, some build scripts need to have commit messages inside the description for task linking, etc.
IMO add syntax to be able to add it to the default if you want it, if not then dont put it in. Would be nice to have the option.
Actually, this issue seems irrelevant as the commits list is directly underneath the description box anyway. Unless you absolutely had to have it somewhere within the message.
Can we please have this implemented this helps a lot in making the review process easier, help devs who are raising PR to make sure that everything is covered.
Would be great if instead of a default static pull request description, we could have a pull request template. The template should allow the inclusion of a commit list, reviewer list, target branch, source branch, etc. using a simple syntax like ${commits}.
Essentially this has been removed by adding templates, so can you plz put the feature back 
I would also like to see the capability. Having something available similar to variables in pipelines would be great.
Please add this capability. I just want to have a custom PR description WITH THE ABILITY to include the commit list.
Would love to be able to interpolate the data suggested by bernd.schotanus in his comment, this would be extremely helpful for our team as well.
Please add the following parameters to be used in a pull request merge template:
- source branch
- target branch
- a short list of included commit messages (first line only)
- an extended list of include commit messages (full commit messages)
- optionally include author/committer, date of each included commit
The commit list helped us to send release notes to our Product Owner.
We have this workflow:
feature-branch-xyz -> develop (automatically deploy to testing)
develop -> master (automatically deploy to staging, send release notes to PO)
master -> production (automatically deploy to production)
We're sending simple text mails to our PO for approval before rolling out to production. The commit list in the PR description was very useful for this.
We do make code reviews for every PR which goes to develop and the template is really useful there.
We just started using default pull request descriptions and instantly had multiple developers request to be able to use their commit messages alongside the PR template. Please let us have both! As it is right now we'll have to choose between the two.
dparrish
I'm following up on 4fab1a620c9f 's comment from 4th June this year. We've just discovered the availability of custom pull request templates, which fits quite nicely with what we want to put in ours, BUT what we normally do on our Data Center instance is add stuff around the default list of commits, rather than replace them. With this variable in place we ought to be able to get the best of both worlds, but I've tried it on Data Center and either it's not supported/doesn't work, or I've done it wrong