1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues


Issue #9582 on hold

Sticky Destination for Branch (BB-10697)

Mike Holdsworth
created an issue

I use the Git Flow workflow and all features start from the develop branch.

Please make the Originating branch (develop) the "destination" branch for merge activities. This will prevent people (authorised peeps like me!) merging to the wrong branch.

Comments (5)

  1. Andy Dennie

    +1 for defaulting the pull request target branch to the original branch that the feature branch originated from. The current approach of defaulting to "master" is an accident waiting to happen.

  2. Martin Lockett

    Pull requests use what is configured as the main branch as the destination. To prevent accidents you could change the main branch in the bitbucket repo configuration to "develop" and add "master" to the branches that can't be deleted. I don't know if this will have any negative side effects though

  3. Log in to comment