How Can I Turn Off Prepopulated Destination Branch?

[Steven Varndell]

When creating a PR Bitbucket tries to guess what destination branch you want to merge to, and it prepopulates the field. It's almost always wrong.  Can this prepopulation be turned off? It's just asking for a branch to be merged somewhere it doesn't belong

[Patrik S]

Hello @Steven Varndell ,

Just adding to @Ulrich Kuhnhardt _IzymesCo_ , while there's not currently an option to turn the branch pre-population in the UI, the way that Bitbucket selects the target branch is based on the branching model configured in the repository or project level: 

• https://support.atlassian.com/bitbucket-cloud/docs/branch-a-repository/#The-branching-model

By default the Production and Development branches are set to the main branch of the repository. You can change those to specific branches according to your workflow.

The configured Production branch is the default target branch for pull requests from release branches.

As for the branch configured as Development branch, it will be the default target for feature branches.

I hope that information helps! Let us know in case you have any questions.

Thank you, @Steven Varndell !

Patrik S

[Ulrich Kuhnhardt _IzymesCo_]

I come across the same problem quite frequently. I don't know a way to turn this off in the UI.

When creating a PR you can use the link that you see when you push the source branch to bitbucket.org (remote) via the git CLI, and add the destination branch as a req param. For example

https://bitbucket.org/<your_workspace>/<your_repo>/pull-requests/new?source=feature/XYZ-123&t=1&dest=develop