←back to thread

Beej's Guide to Git

(beej.us)
1062 points mixto | 5 comments | 05 Feb 25 00:07 UTC | HN request time: 0.399s | source
Show context
scrapcode ◴[05 Feb 25 01:59 UTC] No.42942555[source]▶
I can't help but feel that Git has completely missed the forest through the trees that you can make a 30+ part guide explaining how to use it.
replies(6): >>42942641 #>>42942672 #>>42942768 #>>42943372 #>>42950299 #>>42954886 #
20k ◴[05 Feb 25 03:33 UTC] No.42943372[source]▶
Honestly, 99% of the pain of git is simply because people use it through the CLI. If you use tortoisegit or a visual tool, you don't need to worry about any of this because its self explanatory, and it becomes trivial to use

Learning git like this is honestly just hampering yourself

replies(10): >>42944314 #>>42944637 #>>42944837 #>>42944918 #>>42946240 #>>42946386 #>>42946705 #>>42948452 #>>42948599 #>>43014598 #
wruza ◴[05 Feb 25 05:41 UTC] No.42944314[source]▶
I’ve seen tortoise users break their repo, struggle to understand the issue and then push it through, making it everyone’s problem. Git language is screwed, you cannot unscrew it with a right-click gui because you basically click some latin-looking hieroglyphs that you don’t know either way.
replies(1): >>42945358 #
1. globular-toast ◴[05 Feb 25 07:54 UTC] No.42945358[source]▶
I highly doubt tortoise or any tool can "break" a repo. This might be a sign that you don't understand git either. Now I'm sure it can lead to people who don't know what they're doing doing the wrong thing, but if they're allowed to push somewhere and make it someone else's problem, that's not their fault. They've been forced to use git, so there should be someone else who actually understands git.
replies(2): >>42945665 #>>42949114 #
2. _puk ◴[05 Feb 25 08:31 UTC] No.42945665[source]▶
Ah, we're holding it wrong. Got it.
3. wruza ◴[05 Feb 25 14:42 UTC] No.42949114[source]▶
“Break” doesn’t mean repo integrity corruption. It means that you try to merge a branch, and it shits itself with hundreds of conflicts that shouldn’t appear and/or has changes that may partially revert the progress made by other merges.

if they're allowed to push somewhere and make it someone else's problem, that's not their fault

What? This made zeroest sense of the day. Like, I should walk to their desk and check if a feature branch is okay to push or what?

replies(1): >>42950162 #
4. globular-toast ◴[05 Feb 25 15:45 UTC] No.42950162[source]▶
Usually people make pull requests.
replies(1): >>42950428 #
5. wruza ◴[05 Feb 25 16:01 UTC] No.42950428{3}[source]▶
Yep, with a branch they pushed into. I guess you're ignoring the same context as another commenter elsewhere, probably because your workflow is restricted only to modes that git "supports".