Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-12472

Merge commit messages should use the imperative mood (BB-16101)

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Git commit messages should be written using the imperative mood.

      http://chris.beams.io/posts/git-commit/\\
      https://github.com/git/git/blob/bca181109d6f054d525c71a84963bbdc1f0c40bf/Documentation/SubmittingPatches#L112

      When pull requests are merged by BitBucket, the message starts with 'Merged in".

      Question on StackOverflow:
      http://stackoverflow.com/questions/30721903/is-merged-in-a-commit-message-created-by-bitbucket-or-git

            [BCLOUD-12472] Merge commit messages should use the imperative mood (BB-16101)

            Katarína Lukácsy made changes -
            Resolution New: Won't Fix [ 2 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]

            After reviewing this issue, we determined that it was low priority and unlikely to be worked on in the near future. We appreciate your input, but want to be transparent about our decision to not fix this right now. 

            Katarína Lukácsy added a comment - After reviewing this issue, we determined that it was low priority and unlikely to be worked on in the near future. We appreciate your input, but want to be transparent about our decision to not fix this right now. 

            If not a defaults change, this should at least be an option, either to choose from presets, or be able to create our own templates for the default merge messages. Folks have different styles of commit messages, and for orgs with consistent commit message guidelines, it's annoying to have Bitbucket's automatic comments go against the grain.

            joelbradshaw added a comment - If not a defaults change, this should at least be an option, either to choose from presets, or be able to create our own templates for the default merge messages. Folks have different styles of commit messages, and for orgs with consistent commit message guidelines, it's annoying to have Bitbucket's automatic comments go against the grain.

            mr added a comment -

            How can we get attention to this issue? It is very old. Should we create a new issue and close this one to get attention?

            mr added a comment - How can we get attention to this issue? It is very old. Should we create a new issue and close this one to get attention?
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3537926 ] New: JAC Suggestion Workflow 3 [ 3591746 ]
            Geoff created issue -

              Unassigned Unassigned
              980f4bec9c34 ricsantos
              Votes:
              9 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: