Cross-repository pull requests in Bitbucket Server and Data Center

Still need help?

The Atlassian Community is here for you.

Ask the community

Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.

Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible


Pull requests can be created between two different repositories, as long as they belong to the same hierarchy.

Repos in the same hierarchy are those repos related to each other through forking.

This means cross-repo pull requests can be created between a fork and its upstream/parent/ancestor repo(s) and vice versa.

Note that there can be several levels of forks, up to a maximum depth of 5 (see: Repo cannot be forked. Fork hierarchies are limited to a maximum depth of 5)

For example:

  • original-repo.git is created
  • original-repo.git is forked to create fork-1.git
  • fork-1.git is forked to create fork-2.git
  • fork-2.git is forked to create fork-3.git
  • fork-3.git is forked to create fork-4.git
  • fork-4.git is forked to create fork-5.git

All of the repos above belong to the same hierarchy, so cross-repo pull requests can be created between them.

For example, a pull request can be created from original-repo to fork-5:

Related Link

There is also a feature request to support pull requests between repositories in a project:

BSERV-4577 - Getting issue details... STATUS

Last modified on Dec 5, 2022

Was this helpful?

Provide feedback about this article
Powered by Confluence and Scroll Viewport.