Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-10559

Allow configuring a pattern for pull request merge commit messages


    • 51
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.


      Atlassian status as of Jan 2022

      Hi everyone,

      Thanks to everyone for voting and commenting on this suggestion. Your input in the comments helps us understand how this affects you and what you're hoping to accomplish with Bitbucket Data Center.

      We spend a significant amount of time determining our product investments in Bitbucket Data Center. Unfortunately, we are not planning to address this suggestion in the next 12 months. In the last year, we have resolved many of the highly voted suggestions like Reviewer groups, Pull request description templates, capability to enable/disable source branch deletion on merging pull requests and our upcoming roadmap includes a number of other top voted suggestions, including repository archiving. Please check out our public roadmap for more details on the coming soon and future items.

      I understand that this may be disappointing, but it’s important for us to be open, honest, and transparent with our customers. Product feedback is collected from many different sources and is evaluated when planning the product roadmap. You can learn more about our process here.


      Anton Genkin
      Product Manager - Bitbucket Data Center & Server

       Original suggestion

      BSERV-8384 added the ability to control the subject in pull request merge commit messages, but the use of {}log{-} still can't be configured. A further improvement would be to introduce the ability to configure a pattern, allowing repository (and project, ideally) administrators to configure a fixed pattern for how merge commit messages should be structured. This pattern would include a known set of placeholders to allow placing well-known details as desired, with one placeholder representing -log output (though it would only be supported at the end of the message).

            Unassigned Unassigned
            bturner Bryan Turner (Inactive)
            197 Vote for this issue
            104 Start watching this issue