I was trying to learn git and after searching a bit, I finally found some good open-source tutorials. Specifically, I followed those two tutorials, in this order:

  1. https://ohmygit.org/ (a computer application)
  2. https://learngitbranching.js.org/ (a website)

The second seems to cover a bit more advanced topics (it teaches more thoroughly about remote repositories)

Also after an alternativeto search, I found two more open-source resources:

  1. https://github.com/vishal2376/git-coach (an android application covering the very very basics)
  2. https://github.com/jlord/git-it-electron (An old computer application)

PS. Prior to these I had a basic git course, which I think wasn’t enough, but probably helped me either way and after this I had checked some git resources, which gave more of a rounded knowledge about git and I think are worth metnioning:

  1. https://jdsalaro.com/tutorial/git/index.html (this person is here on lemmy too)
  2. https://tom.preston-werner.com/2009/05/19/the-git-parable.html
  3. https://missing.csail.mit.edu/
  4. https://docs.codeberg.org/git/clone-commit-via-cli/
  5. https://github.com/SimonSchubert/LinuxCommandLibrary

Lastly, there’s the pro git book as well for anyone who wants to go even deeper: https://git-scm.com/book/en/v2

    • Ephera@lemmy.mlEnglish
      2·
      6 days ago

      It’s a version control system, in the absolute broadest sense of the word. You can look at the version of your code, you had yesterday. And your mate can create their own version of your code, which they can later send to you and you can combine it with your version.

      So, in some sense, it’s a time machine and in the other sense, it’s the basis for how collaboration in software development works at all.

    • Blastboom Strice@mander.xyzOP
      1·
      4 days ago

      Haha, this was the first tutorial I was given, though for the reasons you mentioned I didnt follow it. Seems good tho😅

  • Swordgeek@lemmy.ca
    4·
    6 days ago

    It’s not at all gamified or fancy, but I find the official documentation to be excellent - a step well above the norm these days.

    Bonus: Downloadable as an epub or pdf, creative commons license, and regularly updated.

  • A_Union_of_Kobolds@lemmy.world
    4·
    6 days ago

    Oh god I’m just starting to learn a little shell and Python and now I find out git isn’t just a website with code on it

    I reckon ill be using this bookmark for a while…

    • easily3667@lemmus.orgEnglish
      11·
      6 days ago

      Just use a UI like vscode or git kraken

      Knowing “how to use” the git command line is an exercise in delusion. You will only know the same small piece the UI tools know and if you get in trouble you’re going to stack overflow.

      • Muehe@lemmy.ml
        3·
        6 days ago

        Just my 2¢ but disagree on this one. Where GUIs are usually powerful but inflexible, the CLI is both powerful and flexible. And getting into trouble usually means you have a print on the console that tells you exactly what happened and what concept or command to look up.

        Matter of opinion and goals I guess, but if you want to understand git as a tool I recommend learning the CLI.

        • easily3667@lemmus.orgEnglish
          1·
          3 days ago

          What UIs have you tried? The ones I’ve used are completely flexible. Checkboxes for days.

          • Muehe@lemmy.ml
            1·
            3 days ago

            A ton, like the ones integrated in many editors/IDEs, GitHub Desktop, the one with the little turtle icon, forgot its name… Using gitk all the time. Don’t get me wrong I have nothing against a GUI, just saying I had a much better learning experience with git once I started using the CLI and man pages instead of a GUI and random tutorials for them. It’s just a lot more accessible and better documented in my experience.

            • easily3667@lemmus.orgEnglish
              11·
              2 days ago

              Ah…so just the bad ones. Tortoisegit is God awful, stuck in 1999. GitHub desktop is barely a client. Etc

              Of that set the only one worth any damn is the one build into vscode.

              That having been said you just indicated you enjoy reading man pages for the git command line, something literally nobody enjoys. So maybe you are just a special ❄️.

              • Muehe@lemmy.ml
                2·
                2 days ago

                Tortoisegit is God awful, stuck in 1999.

                If it works don’t fix it. Not that it’s my go-to.

                you just indicated you enjoy reading man pages

                I have indicated that I do it, not that I enjoy it. But yeah, I prefer it to skimming 20 verbose blog posts and outdated Stackoverflow questions to find one that is actually related to my specific use case. And often enough the search results will be online versions of the man pages anyway. Not quite sure why you are so hostile about it, I just said “read the docs” basically.

  • 0ops@lemm.ee
    3·
    6 days ago

    Probably the worst way to learn git is “as-you-go” in an actual project. Unfortunately that’s a common way to start, that’s definitely how I started. If I had to learn it again or teach it to somebody else, I’d make a super simple application, like a “Hello World” webpage, and learn and gain confidence with that.