Is it possible to prevent forked repos defaulting their pull requests pointing to the original?

I'm working on a project that will soon require a lot of separate repos all based off of an initial structure. I've already made a "base" repo with the correct structure and tools and now I simply need to fork it, add in the new repo-specific development. I can then simply pull from the upstream repo to update tools and such.

The issue is with Pull Requests. On this forked repo, when I create a pull request, it defaults the repo to the original repo and not this new repo. How do I either have this default to the new repo or how do I stop the original repo from accepting PRs from forks?

1 answer

0 votes


Hi Jake! I found a similar question in Community which I think can help you, I'd recommend having a look at the responses from Roger Barnes on this thread When creating a Pull Request in a Fork...

There's also a Feature request you might be interested in, you can find it at  Make it possible to configure default destination. You can vote for it to increase its popularity, leave a comment or watch it to receive updates.

Hope that helps!


Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

1,959 views 7 10
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you