git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Rewriting the Git tutorial to cover less content

From
Julia Evans <julia@jvns.ca>
Date
Sep 25, 2026, 16:08 UTC
Message-ID
<bd5d9451-ac5a-4274-9a7a-57ae99864fe9@app.fastmail.com>
In-Reply-To
<20260925082723.GB1493716@coredump.intra.peff.net>
Hello!

I'm working on a patch series to replace `gittutorial.adoc` with a completely rewritten tutorial, since a lot has changed since it was originally written.

The new tutorial will cover much less material: just `git init`, `git add`, `git commit`, `git status`, `git diff`, `git push`, `git config`, and `git remote add`. One choice that might be controversial is that I'm not covering branches, though I think it would probably make sense to write a second tutorial on branches and using Git to collaborate later.

The reason to cover fewer commands is that even this smaller set of commands is a lot for beginners to absorb. I've already gotten feedback from a test reader that they appreciated the "you can stop here!" in the middle of the tutorial, since they didn't feel like they could absorb any more information at that point.

If you'd like, you can read the current draft here: https://github.com/jvns/git/blob/git-tutorial/Documentation/gittutorial.adoc I'm not looking for detailed feedback at this stage since I expect a lot of the details to change, and since right now I'm prioritizing feedback from Git beginners who are trying to learn Git for the first time from the tutorial.

But if folks have major objections to the high-level structure, let me know!

I'm excited about this direction, I've already gotten some positive feedback from test readers, like:

> I can say I liked this tutorial better than any of the other git tutorials I've tried.
and
> I really like the tutorial, it's easy to follow and I learned a lot!

I have some ideas for what to do with `gittutorial-2` too but I'll leave that for another discussion.

thanks! Julia

Previous: Jeff KingNext: Junio C Hamano
Message 16 of 23 in “doc: add more AsciiDoc cross-references”
  1. doc: add more AsciiDoc cross-referencesJulia Evans via GitGitGadget, Sep 22, 2026
  2. Junio C HamanoSep 22, 2026
  3. Julia EvansSep 22, 2026
  4. Jeff KingSep 23, 2026
  5. Julia EvansSep 24, 2026
  6. Jeff KingSep 24, 2026
  7. Junio C HamanoSep 24, 2026
  8. Julia EvansSep 24, 2026
  9. Junio C HamanoSep 24, 2026
  10. Jeff KingSep 24, 2026
  11. Jean-Noël AVILAOct 18, 2026
  12. Kristoffer HaugsbakkSep 23, 2026
  13. Jeff KingSep 23, 2026
  14. doc: add more AsciiDoc cross-referencesJulia Evans via GitGitGadget, Sep 25, 2026
  15. Jeff KingSep 25, 2026
  16. Rewriting the Git tutorial to cover less contentJulia Evans, Sep 25, 2026
  17. Junio C HamanoSep 25, 2026
  18. Julia EvansSep 25, 2026
  19. Junio C HamanoSep 25, 2026
  20. Julia EvansSep 25, 2026
  21. Junio C HamanoSep 25, 2026
  22. Julia EvansSep 28, 2026
  23. Junio C HamanoSep 28, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.