We are using Mercurial as our source repository, and each build shows changes from other branches as "M", meaning that they were supposedly merged into the current branch, but they weren't. Changes that were never merged into the current branch are still showing up as changes made to the current branch.
Also, in some cases, commits from other branches will even kick off builds for the current branch.
How can we get around this issue?
On 31 May, a GDPR-related change went live in the Bitbucket Cloud API that resulted in users not being able to create or edit Bitbucket Cloud Linked repositories in Bamboo. This API update removed t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events