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

Change close after merge to close before merge for Mercurial

    XMLWordPrintable

    Details

    • Feedback Policy:

      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.

      Description

      When using the close after merge option for pull requests in hg you first do the merge and close the branch after that. This leaves the closing changeset as an unmerged head.
      This not only looks messy but also leads to a "creates new remote head" problem if you later create a branch with the same name. You then have to merge the closing changeset or force push the other head.
      If you would change to first closing the branch and then merging the closing changeset this problem would go away and the tree would also look much better.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            75593fe284dc fruechtl
            Votes:
            1 Vote for this issue
            Watchers:
            4 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: