this post was submitted on 29 Jun 2023
9 points (100.0% liked)

Git

3583 readers
1 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 2 years ago
MODERATORS
9
Your Git horror stories (programming.dev)
submitted 2 years ago* (last edited 2 years ago) by canpolat@programming.dev to c/git@programming.dev
 

We all have been there... For the beginner it's easy to mess things up. What are your horror stories with Git?

Link to xkcd

top 9 comments
sorted by: hot top controversial new old
[–] unknowing8343@discuss.tchncs.de 3 points 2 years ago (1 children)

Those first couple months learning git... yeah, it is weird, but once it clicks... you'll be surprised how truly simple it is.

The programming world would be awful without it

[–] mookulator@lemmy.world 2 points 2 years ago (1 children)

Learning git was like every other cool tech thing for me (including the fediverse). People explain it in such a convoluted way. It’s like they think you want to understand the deep theory of it before you get up and running!

Yes, git is more than just a “save box”, but really, new users should absolutely just think about it as a save box. Learn the fancy shit later.

[–] Ascyron@lemmy.one 1 points 2 years ago (1 children)

Honestly this is me. At this point I really should know better but I dont, and every tuorial seems to be speaking a whole new language. Any tips for where to learn this?

[–] cliffhanger407@programming.dev 2 points 2 years ago (1 children)

Joined on a project and the unsupervised junior devs had branches for each developer, even if they were working on the same features. They were copying and pasting each others code into their personal branches to stay up to date.

Spaghetti commits took a while to unwind.

[–] letsgo@lemm.ee 1 points 2 years ago

Not really a horror story because I fixed it with reflog, but it was a bit of a shock when we all suddenly couldn't push to the dev branch. Turns out one of the devs, who insists Git is just like SVN, decided to delete dev and push, and ignore the warnings. Apparently that's OK in SVN.

[–] HunterBidensLapDog@infosec.pub 1 points 2 years ago

As an old programmer who has used git since Linus whipped it up over one frenzied weekend after his spat with the evil BitKeeper and who has studied its mysteries since before most of you were born ... yeah just delete the damn project and download a new version.

[–] qwop@programming.dev 1 points 2 years ago

I've often ended up guessing what things do and messing things up.

One example is when I couldn't remember the difference between git checkout -b and git checkout -B, so in my infinite wisdom I decided to use -B because surely capital letters are better! Tried using it to switch back to a branch, and... Yeah, that was annoying.