I'm reading Atlassian's excellent Git tutorials but I'm confused by one diagram:
https://www.atlassian.com/git/tutorials/syncing/git-pull
It's the 3rd flow diagram from the top.
I think it should be just one line: D - A - B - C - E - F - G
With "Remote origin/master" pointing at C and "Local master" pointing at G.
My experiments using SmartGit (pull rebase option) and GitHub seem to confirm this answer but it seemed more likely I've misunderstood than that Atlassian have made a mistake in their diagram.
They go on say further down: "Many developers prefer rebasing over merging, since it’s like saying, 'I want to put my changes on top of what everybody else has done.'". This statement also seems to contradict the diagram.
If the diagram is right, please explain how to put local changes on top of origin changes so that origin's history is preserved.
I've raised this question on stackoverflow and a few other people also seem to think there is an error in the tutorial diagram (and the comments below it). If so how do I report the bug so Atlassian can fix if for other people reading the tutorials? Thanks.
Hi @Robin Carter and welcome to the Community! Thank you for sharing this detailed post. Our content team has been made aware and is working on a new diagram to upload to the tutorial.
Did you catch the news at Team ‘25? With Loom, Confluence, Atlassian Intelligence, & even Jira 👀, you won’t have to worry about taking meeting notes again… unless you want to. Join us to explore the beta & discover a new way to boost meeting productivity.
Register today!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.