Loading...

XML

Word

Printable

Type: Suggestion
Resolution: Unresolved
Component/s: Repository - Settings General
Labels:
- entFY20-n
- migrated

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.

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.