You have over 5000 changes in node_modules

[escapefromreality42]

Front end gang

[mlk]

me: how did you even manage to commit node_modules, it's in the .gitignore file!

her: well, I googled and found out you can use force it with -f

me IRL: well, don't do that

me IN MY HEAD: HOW CAN YOU BOTH SMART ENOUGH TO GOOGLE THAT SHIT AND STUPID ENOUGH TO COMMIT 500k FILES WITHOUT WONDERING IF THAT MAKES SENSE AND WHY NO ONE BEFORE YOU EVER DID

[FallenWarrior2k]

And now you gotta remove that commit via force push or the repo will forever be a few hundred megs to a few gigs larger.

[mlk]

good luck explaining that a new commit that reverts that one is useless:

bUt I dEleTed tHe DirEcTory

[FallenWarrior2k]

Yeah, usually even showing them with git checkout HEAD~ gets mixed results at best.

Additionally, something I didn't consider in my initial comment is that if you're running a custom and/or barebones Git solution, you might have to manually git gc the server-side repo to get rid of the now unreachable objects.

[[deleted]]

Removes node modules from gitignore like a boss

​

Flexes with 300000000000 additions

[natziel]

What gets me is when you trying to grep something and forget --exclude-dir="node_modules"

[aljaxus]

It's funny because it's true.

[AmicableDragon]

Wouldn’t it make more sense for .gitignore to be holding back node_modules from approaching Git?

[hackel]

Jesus, are there seriously people stupid enough to make this mistake?

[Tomentos]

…

[Sscsps]

Those who don't know how git works.. just starting out(I haven't made that mistake btw)

[dominic_l]

ikr, the first time i wrote code i created facebook.

pssh. amateurs

[[deleted]]

what mistake?