You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
I have two separate projects I am working on and they are each in a different Bitbucket repo. One project, let's call it project A, uses libraries from the other project, we'll call this one project B. Now, sometimes my work will include changes to both project A and project B, which are simultaneous and related to the same open issue I am working on. For example, I may need to work with some new data in project A, which in turn will require an update to project B to actually get the data.
At this point I am making changes to project A, pushing those changes, and opening a new pull request for a feature branch in the repo in which project A resides. At the same time, I am making changes to project B, pushing those changes, and opening a new pull request for a feature branch in the repo in which project B resides.
An issue arises when project A, at the new feature branch, is cloned, but can't be built or compiled because it relies on the feature branch of project B which hasn't yet been cloned. This issue becomes a real problem if project A is reviewed, approved, and merged before project B.
When opening pull requests how do I specify that there is a dependency on one pull request by another, and therefore a pull request cannot be merged before it's dependencies are merged?
We use tasks and the No incomplete tasks merge check to solve this. In the task we put the URL to the related Pull Request and mention that both Pull Requests have to be merged at the same time.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bit late to the party, but here is good news. We have released pull request merge hierarchies in Pull Request Organizr via an intuitive drag and drop method to create multi-level pull request merge dependencies.
Linking and unlinking pull request dependencies
Check out the blog ...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.