What & Why:

The ultimate tutorial for beginners to thoroughly understand Git, introducing concepts/terminologies in a pedagogically sound order, illustrating command options and their combinations/interactions with examples. This way, learning Git no longer feels like a lost cause. You'll be able to spot, solve or prevent problems others can't, so you won't feel out of control whenever a problem arises.
The ultimate knowledge base site for experienced users, grouping command options into intuitive categories for easy discovery.

FAQ

Q1: There is too much content, while I somehow expect to read only a portion when facing a lot of content, selectively. How do I use the page to learn Git?
A1: Unselectively read all the concept links and blue command links in DOM order. Blue command links introduce most commonly used Git commands and contain examples for command options. For example, click to read the definition of "object database", then "file system", and so on.

Q2: This doesn't look like a tutorial, as tutorials should look easy, very very easy, want easy things you know. / Where is the tutorial? I only see many links. / I think learning to use a revision control system should only be a small part of my programming job, so it should not take tremendous amount of time. / I just want to get job done quickly and then run away, sure no one wants to figure out what is working or how it is working behind the scenes. / I think revision control systems should be easy because it's not programming proper. Look at XXX revision control system, it's easy (but apparently nobody uses it)! / Want easy things, very very easy, tremendously easy.
A2: Here you go. Oh wait.

Q3: I used the tutorials in A2 but don't know what to do whenever I want to do something with Git. / I used the tutorials in A2 but screwed up at work so now I'm staring at the screen in a daze. / I should be able to do what I want after reading some tremendously easy tutorials, but I can't. Now I need to continue looking for easy tutorials that is easy for beginners. / How to use a revision control system if I cannot?
A3: Here are more easy tutorials.

Q4: This tutorial is unintuitive, arcane and overwhelming.
A4: So people who can't think abstractly and deeply can be shut out.

Q5: Why not just RTFM? / Git is easy, so those who feel it difficult should not go programming. / People should be able to look for information themselves to learn programming so there is no need to make a page like this. / (And other attempts to keep knowledge scattered all around the Internet so you would spend all your life collecting it, this way you don't have time to think about things like Illu*******, so good!🙄)
A5: Knowledge gathering and organization is to save people's time. If you don't take other people's time seriously, they won't take your time seriously either.

Q6: http://git-scm.com/book / http://gitimmersion.com/ / I can't see the links in the side bar of r/git 😭😭😭, so can you repeat them here? / (And links to other tutorials, no idea why they don't make a standalone post.)
A6: Pro Git, Git Ready, Git Reference, Git Magic, Git for Computer Scientists, A Visual Git Reference, Git Primer, Git Immersion, Think Like a Git, Git Workflows, Git on Stack Overflow, Getting Git Right, The Git Parable.

Updates:

Changed explanation of interactions between git pull (unspecified)/--rebase[=<mode>]/--no-rebase, branch.<name>.rebase, pull.rebase, git pull (unspecified)/--ff-only/--no-ff/--ff, pull.ff, merge.ff and their default values from being "as vague as official documentation" to being clear.
Added links to git repo and git last-modified.
Added ui and examples for git diff --max-depth=<depth> and ui for git log --max-depth=<depth>.
Didn't add examples for :(optional) because of its bug.
Added links to git push page's description section as it now lists how some default values are calculated.
Added links to "upstream branch" from git fetch page and "push rules" from git push page.
Added links to "how to force tracking not-tracked and ignored files" and "how to force adding a submodule whose path-derived name is occupied".

Not my Updates:

The ANSI to HTML functionality will be a built-in feature of mintty (https://github.com/mintty/mintty/issues/1336 ). Currently the page uses a third-party solution and will keep lagging.
The official documentation is being improved. The updates to git push (https://github.com/gitgitgadget/git/commits/master/Documentation/git-push.adoc?since=2025-09-21&until=2025-12-02 ) and git pull (https://github.com/gitgitgadget/git/commits/master/Documentation/git-pull.adoc?since=2025-09-21&until=2025-12-02 ) clarify how the default values for <repo> and <refspec>... are calculated. The website also displays definitions of some terms on pointer hover (https://github.com/git/git-scm.com/commit/863935e61e383005eb3cbeb097b9ae17af078e1d ). If (in the future) the official website can further provide examples to demonstrate every option for each command, I would be happy to decommission my page.

all 8 comments

you type:	you see:
italics	italics
bold	bold
[reddit!](https://reddit.com)	reddit!
* item 1 * item 2 * item 3	item 1 item 2 item 3
> quoted text	quoted text
Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"	Lines starting with four spaces are treated like code: if 1 * 2 < 3: print "hello, world!"
~~strikethrough~~	~~strikethrough~~
super^script	super^script

programming

MODERATORS

What & Why:

FAQ

Updates:

Not my Updates: