Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Why do commits from separate branches in Mercurial show up as "M" for each build?

Eric Bergemann
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 12, 2017

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?

screenshot.png

1 answer

1 vote
Przemek Bruski
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 12, 2017

Do you mean you're seeing changes from unrelated branches showing up in your branch commit list?

Please submit a support ticket via support.atlassian.com. Make sure you mention your Mercurial version and OS in the ticket.

Eric Bergemann
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 12, 2017

Yes, unrelated branches, other branches, any way you want to put it. I'll create a support ticket for this.

 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events