The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)
× Create
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Community resources
Community resources
Community resources
How do you clone a PR when the author's fork is private?
If someone uses the bitbucket web interface to edit a file, create their own fork, and create a PR with the edit, that fork may not be shared automatically with the owners of the upstream repo.
The upstream owners can still view the PR itself, and optionally merge it in the bitbucket web interface, but since the fork is not shared with the upstream owners, they cannot locally add the fork as a remote to pull from, in the event that they want to tweak the change before merging.
Is there something I'm missing here, or do all PR-submitters need to be trained to share their repo with the upstream maintainers?
0 answers
Comments for this post are closed
Community moderators have prevented the ability to post new answers.
Copyright © 2026 Atlassian