Issue #9368 new

Branches: set different default destination branch (BB-10403)

Ben Tatham
created an issue

It seems that in a given repository, there is only one "main" branch. This of course makes sense in most cases.

However, when we want to have a long running "legacy" branch, it would be nice to still be able to use gitflow on that. While Bitbucket does not support gitflow directly, it does tell you that your branch is out of sync with the repo's main branch (when looking at the /{repo name}/branch/{branch name} page).

It would be nice to be able to specify a different "main" branch for a given branch (including specifying none for the legacy "develop" branch, in gitflow parlance).

In our example, we have a regular "develop" branch (and master of course), and then the "feature/foo" branches under it.

For legacy, I created a legacy/develop, legacy/master and use standard gitflow branches under the legacy/ prefix. So in other words, I want to have no main branch for "legacy/develop" and specify the main branch on the "legacy/feature/*" branches.

Comments (4)

  1. Michael Frauenholtz staff

    Hi Ben,

    This is something that we considered when we added the branch list, but did not have time to implement. We have a ticket in our backlog for this. I don't know that we can get to it soon, but we'll let you know here when we've got more to share.

    Cheers,
    Michael

  2. Derek Price

    Yes, I think simply choosing the base branch as the default destination (instead of master) when creating pull requests would simplify things immensely for my team and help avoid a lot of human error.

    branch base.png pull destination.png

  3. Log in to comment