Community
Products
Bitbucket
Questions
Default Pull Request Description - include list of commits

Default Pull Request Description - include list of commits

Hi all,

I want to use the default PR description to prompt our devs into adding certain information, but the list of commit messages is useful and I don't want to lose that. Is it possible to get both? So I can put my default description with prompts at the top, and then at the bottom retain the list of commit messages that a blank default description generates?

21 answers

8 votes

Bump! This is a long requested feature. Can anyone from bitbucket answer this? Thanks

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

2 votes

I would also love to see this. A default template is necessary in a growing team but I really don't like the idea to lose the handy Changelog provided automatically via the commit messages. Maybe it would possible to let us just write something like {{ commit-log }} and on this place the standard list will be included.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

2 votes

Best case would be a simple template engine where I can choose where the list of commits are included but I would be content if there was a checkbox to tell bitbucket to just append the commit list at the end of the description.

In addition it would be nice if the list would update when new commits are pushed to a PR.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

Use {{commit_messages}}.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Wow, thanks a lot, it works!

Where did you find this?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

As we can see Atlassian totally doesn't care about "community"... (creating a "community" space is not enough to build a community, you know that, right?)

Bitbucket is not Number One for a reason...

@ ATLASSIAN @ - How many more years do we have to wait until you will at least bother to answer this request from the "community"?

Is it really so hard for a big IT company to add an option to include commit history within Template with some `{{commitHistory}}` ???

Or, if it's too hard for you, maybe you can at least provide this list below the template (We can copy/paste it where we want, not a problem) - it should not be too hard? A checkbox `[ ] add commits history` or a third option "Template with commits history on the end". It can't be so hard...

It's really frustrating to wait for this feature for so many years...

EDIT:

They added {{commit_messages}} in PR template, here are docs:
https://support.atlassian.com/bitbucket-cloud/docs/pull-request-and-merge-settings/

And... it looks like they added it 3 months after I wrote this comment:

https://jira.atlassian.com/browse/BCLOUD-17743

It's sad nobody from Atlassian bothered to write here on a Community to inform us about this. I've lost a lot of time for adding descriptions manually during this 1 year...

And they really should add info about this variable somewhere in UI to make it easier to find it.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

Hello Atlassian? Anyone home?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

Although we can view the commit messages in the commits section, it would be great if we can have it in the description part along with the default description

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

1 vote

I want to have both a custom default PR description and the commit list too!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

I can't believe this is not already an option. Atlassian, please add support for this!

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

~~Great, today Bitbucket updated the PR layout (obligatory change) - somebody asked for this? IMHO only more clicking in the new one, and actions mixed with comments by default...~~

~~But here they don't even bother to answer for so many years...~~

~~People are asking for a simple feature, but they ignore it and deploy a huge refactor of something that was actually OK already...~~

WOW, we can use {{commit_messages}} in the PR template!

I'm editing my negative comment with pure pleasure! :D

(But I'm still not sure if a new PR layout was a good change... we will see in few days ;) )

Here are docs where they mention it: https://support.atlassian.com/bitbucket-cloud/docs/pull-request-and-merge-settings/

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Is this available in Bitbucket Cloud only?

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Like • Mike P likes this

0 votes

+1. It really shouldn't be too hard to add a feature where the user could type something like @commitlog into the template and it'll expand to the commit messages. While you're at it, something like @commitlogfirstlines would be cool too, where it just inserts first lines.

(That doesn't work, if anyone is reading. It was just a suggestion how it could look.)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 votes

In order for customizing the Pull request description template to be useful there need to be ways to include the list of commits that is included default in the template you construct. If you define your own template today you loose that feature which isn't great. It would be great if you could have an extend-option so you can use default but extend the default template with additional content.