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

Close feature branches in pull requests *before* merging them for hg (BB-6927)

    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

      The way Bitbucket pull requests currently handle branch closing, by merging first and then closing, works against the grain of Mercurial: it creates a dangling head for each branch-closing commit, which clutters the repository history, and frustrates features like hg pull -r <rev> (which won't pull in the closing commits relevant to the target revision).

      For this reason, the usually recommended way of closing and merging branches in Mercurial is to close them before merging them: see e.g. here and here. This makes for a cleaner and more readable history, and avoids the usability problems above.

      Can the branch closing feature for Mercurial repositories be changed to work this way?

      (Alternatively, if there are users who for some reason insist on the current close-after-merge behavior, can both options be supported?)

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            bffdbb239501 Pi Delport
            Votes:
            12 Vote for this issue
            Watchers:
            14 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: