Why can't I specify another repository for pull request in BitBucket?

As described on SO some time ago, http://stackoverflow.com/questions/29633910/why-cant-i-specify-another-repository-for-pull-request-in-bitbucket/33667065#33667065

In steps:

1) My repo was created

2) Team repo was imported off my repo

3) Branch was done on my repo

4) PR was created

PR cannot target team repo, despite same history of commits.

 

Why is that so?

 

2 answers

I am also interessiert in that.

Why do i have to fork a repo, so i can create pull-request to it, instead of simply selecting ALL available repositories (for that i am Admin)

This is also a major issue for me, and something I hope they fix soon.

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

2,034 views 1 5
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