Git gud

Git gud

133 comments · 95% upvoted · source · other discussions

comments

sh0rtwave

Do you claim to NOT know why this happened?

NoLifeGamer2 [OP]

IDK not my problem I'm resigning later anyway

stilldebugging

Wow, that’s an extreme reaction to a bad git merge. Or… is it?

alaskanloops

I've copied code from my IDE to a text editor, threw away my branch, pulled Master, create new branch, then copy code line by line from text editor back to IDE instead of dealing with a gnarly merge conflict before. I call this the "Nuclear Option".

[deleted]

[deleted]

LiamMeron

God, I hate this shit. Every feature I work on has me touching nearly the entire codebase. How did I inherit the maintenance of this ball of spaghetti program and how do I un-inherit this?

danielv123

This becomes less of a problem as the project grows in my experience.

LiamMeron

This is a legacy application. It's unfortunately already grown into this shape...

danielv123
Xanvial

That's just rebase with extra steps

vale_fallacia

Ooh-la-la, someone's going to get laid in college.

i_sigh_less

That's more or less the same as

git merge -s ours

isn't it?

normalmighty

It is, but a shocking number of people don't know any git features beyond the basics you use every day.

alaskanloops

Yep this was me at the time.

jjbugman2468

Yup. Been there, done that. I’d been at the merge conflict for hours and finally decided to do this. Done in less than 30 mins.

MegabyteMessiah

Thought I was the only one

casce

I can definitely see situations where a bad merge would justify quitting your job.

stilldebugging

Yeah, me too. Except that if I changed jobs I’d start with nothing when I ctrl-r. Existential crisis.

dagbrown

Wasn't there an enormous outage just last week caused by, essentially, a bad git merge?

_GCastilho_

*Vsauce music starts*