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'm new to git and sourcetree, and I recently encountered an issue where there is no merge commit and all my branches are collapsed after I merged develop into main (first merge was the UPDATE:increment version to 1.0.0 commit). No matter what branch I switch to, it always displays as a single line. If I make changes to a single branch, it doesn't represent them graphically as distinct branches. This can be seen below:
But in another repo, everything functions as normal:
Has anyone encountered this before? I tried to search for a solution or cause, but didn't see anything. The only thing that stands out to me is that one is showing a remote HEAD while the other does not.
Thanks for the help!
Managed to solve the issue.
I'm not sure why, but the one repo was merging via fast-forward so it was not creating a commit.
After performing a hard reset of the main branch to the initial commit, I selected "create a commit even if merge resolved via fast-forward" and now the branches and merge commit are present.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.