Learn Programming

1625 readers

1 users here now

Posting Etiquette

Ask the main part of your question in the title. This should be concise but informative.
Provide everything up front. Don't make people fish for more details in the comments. Provide background information and examples.
Be present for follow up questions. Don't ask for help and run away. Stick around to answer questions and provide more details.
Ask about the problem you're trying to solve. Don't focus too much on debugging your exact solution, as you may be going down the wrong path. Include as much information as you can about what you ultimately are trying to achieve. See more on this here: https://xyproblem.info/

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago

MODERATORS

Ategon@programming.dev

JaumeI@programming.dev

bugsmith@programming.dev

Git for Beginners: Zero to Hero 🐙 (jdsalaro.com)

submitted 1 year ago by ericjmorey@programming.dev to c/learn_programming@programming.dev

9 comments fedilink hide all child comments

Although I prefer the Pro Git book, it's clear that different resources are helpful to different people. For those looking to get an understanding of Git, I've linked to Git for Beginners: Zero to Hero 🐙

The author of "Git for Beginners: Zero to Hero 🐙" posted the following on Reddit:

Hey there folks!

I've rewritten the git tutorial. I've used over the years whenever newbies at work and friends come to me with complex questions but lack the git basics to actually learn.

After discussing my git shortcuts and aliases elsewhere and over DMs it was suggested to me that I share it here.

I hope it helps even a couple of y'all looking to either refresh, jumpstart or get a good grasp of how common git concepts relate to one another !

It goes without saying, that any and all feedback is welcome and appreciated 👍

TL;DR: re-wrote a git tutorial that has helped friends and colleagues better grasp of git https://jdsalaro.com/blog/git-tutorial/

EDIT:

I've been a bit overwhelmed by the support and willingness to provide feedback, so I've enabled hypothes.is on https://jdsalaro.com for /u/NervousQuokka and anyone else wanting chime in. You can now highlight and comment snippets. ⚠️ Please join the feedback@jdsalaro group via this link https://hypothes.is/groups/BrRxenZW/feedback-jdsalaro so any highlights, comments, and notes are visible to me and stay nicely grouped. Using hypothes.is for this is an experiment for me, so let's see how it goes :)

https://old.reddit.com/r/learnprogramming/comments/14i14jv/rewrote_my_zero_to_hero_git_tutorial_and_was_told/

top 9 comments

sorted by: hot top controversial new old

[–] jdsalaro@feddit.de 0 points 1 year ago (1 children)

Hey there, author here in case you folks have questions 👍🏼

[–] canpolat@programming.dev 0 points 1 year ago (1 children)

Git has a steep learning curve and everyone has a different way of learning things. So, kudos for taking the time for trying to clarify things.

Some unsolicited feedback: Most of the time, I see people struggling with git checkout. And it's not without a reason. checkout has too much responsibility. Or, to put it in a more nuanced way, from the plumbing point of view it has a single responsibility, but from the user's point of view it has many. So, I try to suggest using switch and restore instead of checkout when appropriate. But old habits die hard, I still use checkout for both of those things. I found a concise Stackoverflow answer. Maybe it would also clarify things for your audience?

[–] jdsalaro@feddit.de 0 points 1 year ago (1 children)

from the plumbing point of view it has a single responsibility, but from the user's point of view it has many

I wholeheartedly agree, I'll add this edit to my backlog !

[–] canpolat@programming.dev 0 points 1 year ago (1 children)

I see that your blog focuses on Git. I'm not sure if you are aware, or not, but there is a Git community at https://programming.dev/c/git. Feel free to share links to your blogs.

[–] jdsalaro@feddit.de 0 points 1 year ago

It's not really that my blog focuses on git, rather than that's what I chose to get active again with :) I've got many posts drafted but decided to start with topics I'm well acquainted with and newbies feel are challenging. I'll post there !! Thanks 👍🏼

[–] santa@sh.itjust.works 0 points 1 year ago (1 children)

Something I’ve been trying to figure out for a bit is how to restore hunks like gitk or vscode do via gui. It seems like it is an augmentation combination of cherry-pick and/or rebase. I prefer command-line, but if I need to do this one operation I fire up a gui, or restore lines with patch.

Any idea how to do it, or how it is done behind scenes in gui?

[–] jdsalaro@feddit.de 0 points 1 year ago (1 children)

What about git checkout -p HEAD^ myfile ?

[–] santa@sh.itjust.works 0 points 1 year ago (1 children)

Would that only revert part of a file?

[–] jdsalaro@feddit.de 0 points 1 year ago

Try it and report back