Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

How to default PR's to forked repo instead of original source repo?

We have some repositories, that are just slight variations on a previous done work. As such, we created them by forking the repository that has similar code that will be used as a starting point. However, since it is a fork, each time in the new repo we open a PR, by default it will do it towards the original repository, instead of remaining inside the repo.

The fork was basically only intended to create a copy, there is no point in keeping them linked or even in sync. The two repositories, old and new, should be able to behave independently from each other.

However, I find no option to sever the link between the both repositories, nor do I find a setting that allows me to select the preferred target for the PR, so I can put it to the current repository.

1 answer

1 accepted

0 votes
Answer accepted

Hi @Mark Nelissen,

I'm afraid that it is not possible for Bitbucket users/admins to do that, however it is possible for the support team to remove the fork relationship between two repositories.

  • If you feel comfortable sharing the names of the repos (masked, with some asterisks in the name, if you don't want to share their full name publicly), I can do this.
  • Alternatively, since you're a member of a workspace on a paid plan, you can create a ticket with the support team and ask them to remove the fork relationship for certain repos.
    The ticket will be visible only to you and Atlassian staff, so you can share the repo URLs there. The ticket can be opened via, in "What can we help you with?" select "Technical issues and bugs" and then Bitbucket Cloud as product.
  • I can also create the support ticket for you if you prefer that, please let me know.

We have a feature request to allow admins to remove the fork relationship between two repositories:

You can add your vote in that feature request (by selecting the Vote for this issue link) and add yourself as a watcher (by selecting the Start watching this issue link) if you'd like to get notified via email on updates.

If you have any questions, please feel free to let me know.

Kind regards,

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events