When we create pull requests, the default repo is the parent repo from which we are forked from.
i.e. Repo A, and Repo B is a fork of A.
I create a pull request in Repo B, it sets up a default PR aimed at Repo A. The description field contains a diff between the two repositories (which you can imagine is a massive list) and this opens up opportunities for mistakes.
I don't see any options within Bitbucket to change the target.
In this tutorial, in the first screenshot you can see that there is a dropdown for the target branch: https://support.atlassian.com/bitbucket-cloud/docs/create-a-pull-request-to-merge-your-change/
After you change the target branch, the diff will update.
No, my issue is the default target repository. I've created an imaginary pull request diagram.
Our Repository is called "thisrepo", and it was forked from "parent_repo". When we open a PR from "thisrepo", the default target repository is "parent_repo" which we do not want.
I've looked in Advanced settings and I only see an option for default target branch, which does not seem to affect the default target repository.
Does your repository need to be a fork? If you are not using the forking workflow, then you could clone the original repository (instead of forking it) and the default destination branch for pull requests would be the cloned copy rather than the original that was forked.
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events