)]}'
{
  "commit": "8f0635da918be894dab8381735c0a50ef4ce66bb",
  "tree": "99261328f1491e5e56ae080bae05b201bb559f2b",
  "parents": [
    "d21f0d7072fae0f858a1050a07b0e698839c0860"
  ],
  "author": {
    "name": "Julia Evans",
    "email": "julia@jvns.ca",
    "time": "Fri Oct 30 20:56:27 2026 +0000"
  },
  "committer": {
    "name": "Junio C Hamano",
    "email": "gitster@pobox.com",
    "time": "Fri Oct 30 15:29:32 2026 -0700"
  },
  "message": "doc: add new Git tutorial for beginners\n\nIntroduce Git in two parts:\n\nSteps 1-7: Create an empty repo \u0026 make 2 commits (`git init`,\n`git add`, `git commit`, `git status`, `git diff`)\nSteps 8-12: Push the repo to a remote host like GitHub or GitLab\n(`git remote add`, `git push`)\n\nSome design choices:\n\n- Only use commands present in 2.23.0 (when `git switch` as introduced),\n  to support older versions of Git.\n- Introduce a much smaller set of commands than the old tutorial, to\n  keep the tutorial quick (doable in an hour). Some users found it to be\n  very fast and some wanted to stop early (after step 7) so this seems\n  to be a good balance.\n- Have users start with an empty repository instead of an existing\n  project, because many of the testers did not have an existing project\n  to test, or were scared of using an existing project.\n- Add a troubleshooting section, since in the testing some users got\n  extremely stuck (for 4+ hours) on minor issues like needing to say\n  \"yes\" when SSHing to a new host.\n- Don\u0027t explain branches, because explaining branches and collaboration\n  is complicated and deserves its own tutorial. Instead just tell users\n  we\u0027re not going to explain them in this document.\n- Tell users to set their default branch to `main`, because many Git\n  hosts use it as their default branch and it really simplifies things.\n- Keep it as vendor neutral as possible, while acknowledging the reality\n  that Git hosting services like GitHub, GitLab, etc are extremely\n  popular. Do this by creating the repo locally and then optionally\n  pushing it later.\n- Use SSH for authentication, explaining how to set up SSH in the\n  easiest way possible (with disclaimers to check your security team\u0027s\n  policy if applicable since the \"easiest way\" may not be the best), and\n  giving some instructions for how to translate an HTTPS URL to an SSH\n  URL.\n- Use Git Credential Manager for authentication on Windows, since it\u0027s\n  simpler, SSH auth is a very \"unixy\" thing to do,  and GCM comes with\n  Git for Windows\n- Warn people about how `vi` is the default text editor and give some\n  instructions for how to escape\n\nAt least 20 people have successfully completed it, and feedback was\nincorporated from problems the testers ran into.\n\nHelped-by: D. Ben Knoble \u003cben.knoble@gmail.com\u003e\nCo-authored-by: Marie Claire LeBlanc Flanagan \u003chello@marieflanagan.com\u003e\nSigned-off-by: Marie Claire LeBlanc Flanagan \u003chello@marieflanagan.com\u003e\nSigned-off-by: Julia Evans \u003cjulia@jvns.ca\u003e\nSigned-off-by: Junio C Hamano \u003cgitster@pobox.com\u003e\n",
  "tree_diff": [
    {
      "type": "add",
      "old_id": "0000000000000000000000000000000000000000",
      "old_mode": 0,
      "old_path": "/dev/null",
      "new_id": "18b2d28d84605fc72decb902ce7567c58d55024e",
      "new_mode": 33188,
      "new_path": "Documentation/gittutorial.adoc"
    }
  ]
}
