We couldn't load the project sidebar. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-8384

Allow editing of the full commit message when merging a pull request

XMLWordPrintable

    • 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.

      Currently when you merge a pull request through the Stash web front-end, you do not have full control of the commit message. This leads to polluted commit logs on master.

      In particular, my group would like to use the squash merge strategy and have clean commit messages once the pull request is accepted. The only way to work around this issue that I am aware of is outlined here:
      https://answers.atlassian.com/questions/283338/pull-requests-squashed-commits-remote-merges?continue=https%3A%2F%2Fanswers.atlassian.com%2Fquestions%2F283338%2Fpull-requests-squashed-commits-remote-merges&application=acac

      This behavior means that what should be a 1 click operation is turned into a more laborious and error prone process.

        1. 5.8 merge dialog.png
          5.8 merge dialog.png
          59 kB
        2. max-commit-summaries.png
          max-commit-summaries.png
          24 kB

          Form Name

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Bitbucket Data Center'
            1. Bitbucket Data Center
            2. BSERV-8384

            Allow editing of the full commit message when merging a pull request

            XMLWordPrintable

              • 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.

                Currently when you merge a pull request through the Stash web front-end, you do not have full control of the commit message. This leads to polluted commit logs on master.

                In particular, my group would like to use the squash merge strategy and have clean commit messages once the pull request is accepted. The only way to work around this issue that I am aware of is outlined here:
                https://answers.atlassian.com/questions/283338/pull-requests-squashed-commits-remote-merges?continue=https%3A%2F%2Fanswers.atlassian.com%2Fquestions%2F283338%2Fpull-requests-squashed-commits-remote-merges&application=acac

                This behavior means that what should be a 1 click operation is turned into a more laborious and error prone process.

                  1. 5.8 merge dialog.png
                    5.8 merge dialog.png
                    59 kB
                  2. max-commit-summaries.png
                    max-commit-summaries.png
                    24 kB

                        bturner Bryan Turner (Inactive)
                        4c762d6af390 Corey Steele
                        Votes:
                        232 Vote for this issue
                        Watchers:
                        121 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              bturner Bryan Turner (Inactive)
                              4c762d6af390 Corey Steele
                              Votes:
                              232 Vote for this issue
                              Watchers:
                              121 Start watching this issue

                                Created:
                                Updated:
                                Resolved: