That is strange. Based on the portion of the commit messages you included, it looks like the merge commit is being rendered before (below) the commit it was merged from (the 2.4.0 tag).
Do you have your graph set to use Date Order or Ancestor Order?
I had it set to Date Order. When I switch to Ancestor Order, the branches show up correctly. Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
So it sounds like somehow the merge commit has an older timestamp than the tag commit that was merged in. Maybe somebody's machine has their time misconfigured slightly?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's possible. The merge occurs as part of a build plan that's run in Bamboo; I will check into it. Thanks again!
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.
ok, that's weird.
If it's a merge commit, there must be another branch that was merged into it, right? So the weird thing is why is it not showing that branch?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.