Cross-repository pull requests in Bitbucket Data Center

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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

Summary

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:

(Auto-migrated image: description temporarily unavailable)

Solution

Related Link

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

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.