YOU ARE A FUCKING SOFTWARE DEVELOPER WITH AT LEAST A LITTLE TRAINING FOR THE LOVE OF GOD PLEASE STOP FUCKING UP THE GIT REPOSITORY BY COMMITTING THE GODDAMN NODE_MODULES

How does one even manage to do that if the .gitignore is set up properly?

@kamen He deleted the gitignore. No fucking clue why. Scared to ask. Just gonna led the project lead deal with this one

Sharing is caring!

And then he complains about slow git pushes!

I inherited a codebase like that once. 20k+ files. It took 5 minutes to get latest on the repo.

I tried to fix it once, but none of the package.jsons (there were 3, for some reason) were up to date, and probably never had been. There were so many conflicts, I eventually gave up.

That was a waste of a week.

I committed a zip file of the binaries into my branch once. Man, that was embarrassing. Ballooned the repo to 2gb just to add insult to injury.

Didn't take long to fix, but shit happens.

Haha npm goes brrrrrrrrr

Both Npm and Git should be like “shit , you really want me to move all this crap to git? You fucked up, I got you, I’ll fix your git ignore settings.”

I need to make a lambda runtime and require the git executable. So I’ll likely be committing git to git… help

@bashleigh yo dawg, I heard you like git

@recfab yessss perfect!! But I’ve decided on making a runtime instead. AWS is confusing as fuck

i did this similar rant long time ago ahahahahah

https://devrant.com/rants/2089042/...

🤣🤣🤣🤣🤣 this one never gets old. Another good one I've seen twice in less than 6 months is, parallel package-lock.json and yarn.lock

I tried to explain that we should only have one. But it didn't take.