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.
So, I have a local branch "feature/feature1" that branches off "develop".
While I am working on the feature branch I make 3 commits. In the meantime, someone makes 18 commits on the develop branch.
As a responsible git user before merging my changes into "develop" I rebase "feature/feature1" onto develop.
Of course now "origin/feature/feature1" is not up to date with "feature/feature1" anymore. The top most entry in the git history graph is now "feature/feature1".
It is 18 commits ahead of "origin/feature/feature1" and 3 commits ahead of "origin/develop".
However, Sourcetree tells me that it is "18 commits ahead and 3 commits behind".
Should this not be "18 commits ahead and 3 commits ahead" instead?
Or am I understanding something wrong?
Hello! This might be a bit hard to figure out without the picture of the graph itself, but that "3 commits behind" might be referring to the ancestor order rather than the date order. Could you post a picture of the graph? Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.