Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Commits labeled "M"

I see some commits are labeled "M" in the Bamboo Code Commits Tab (and repeated on the Summary tab). What does this mean?

3 answers

It means that those commits were the result of a merge.

1 vote

They are merged commits. Idea is if you merge multiple commits and then the build fails we only notify the person doing the merge rather than marking half your team as responsible. To indicate the commits that are not taken into account when we determine responsibility, notifications and so on, we flag them with 'M'

How exactly bamboo understands, which new commits were "merged" and which were not? Git does not know which branch a commit was originally committed into. I'm interested in a general case, when we do not use pull requests and perform merges manually.

We use heuristics that checks at ancenstry path between previous and the current build. If a commit is not on the path, it's most probably a 'merged' commit. Obviously, this doesn't always work, but is good enought for typical setup.

Fair enough. Is this something more complicated than simply walking to the first parent each time? Is it documented? And can we change this behavior?

They are merge commits.

Hmm, I don't see them in my Bamboo install (5.10.0).

They make a lot more sense if you install one of the commit-graph add-ons available in marketplace.atlassian.com and the look at them in Bitbucket Server (search for "commit graph"):

 

490a7183-2c90-459e-8773-3429085b1f7f.png

 

I recommend Bit-Booster Commit Graph.

But I'm biased.  I'm the author of that add-on.  smile

Perhaps I should port it to Bamboo!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo Data Center - Early Access Program

G’day Bamboo customers, The wait is almost over! We are in the final stages of work on the first release of Bamboo Data Center, our self-managed enterprise offering of Bamboo. This Data Center offe...

952 views 0 16
Read article

Community Events

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

Events near you