55

Everyone in my company prefers solving git issues rather than `rm -rf` & `git clone`

Feels like I'm working with a team of geniuses. 😂

Comments
  • 4
    Or maybe they have too much free time to spare 🤔
  • 17
    Only time I’ve had to delete and reclone was when Git became corrupted and couldn’t track changes.

    Gits not that complicated...
  • 5
    @C0D4 same here I once fucked up something and git stopped working for my project, that's when I had to reclone
  • 7
    @gitpush I know right. I’m no “pro” of Git but I really don’t understand people’s problems with it sometimes.

    Oh, I think I’m having a merge conflict with your avatar.
  • 4
    @C0D4 hahaha lets keep our avatar branches separate
    As for git the only headache I used to get was with merging conflicts, but IDE/VS Code have advanced tools now and no more headaches
  • 3
    @gitpush i do enjoy vsCode’s conflict resolution. Click accept and save and away you go 😎
  • 2
    @C0D4 yup best thing I saw so far
  • 3
    Team of geniuses for using a tool in the way it was written, huh? The bar seems kinda low where you live.
  • 2
    @piehole ever heard of the word sarcasm? :P
    Even I, always solve issues... Because if there is something wrong, it will happen only when you have code that hasn't been pushed yet, I wouldn't want to lose it.
  • 1
    Or maybe they have a real problem like having committed a file that's larger than the server side hook allows... This let me introduce interactive rebase to everyone ^^
  • 0
    It’s called being lazy. Faster to copy files, rm, clone and copy back the to understand git. We got them idiots too.
  • 1
    Fwiw, I used to be in the "sod it, drop and reclone" camp - but it's definitely worth taking the time to learn git properly. You may find yourself using features you never knew existed on a daily basis if you do (feature branches, local commit history rewriting etc. is incredibly useful and powerful if you're comfortable with it.)
  • 1
Your Job Suck?
Get a Better Job
Add Comment