8
FlipFloop
22d

I don’t know why/how, but some guy in my team put the node_modules folder on GitHub.

This person ran *npx create-react-app* and for whatever reason probably DELETED the .gitignore.

I had to fix it of course, and in the meanwhile I forgot to switch branches before changing everything, making git crash because switching branches with +4 million lines of code deleted was too much.

Why don't they let experienced front-end devs initialize projects? I don’t understand.

Comments
  • 2
    I mean... why not?

    Not like I haven't ever committed node_modules due to some circumstances.
  • 5
    @N00bPancakes
    Deleting .gitignore is a double fuckup though
  • 0
    @SortOfTested It's a weird choice and I would wonder how it happened but if they just started a project maybe they meant to just replace it and forgot a step.
  • 2
    @N00bPancakes
    That just means you're not checking your stage before committing. Definitely shame on you 😋
  • 3
    @SortOfTested If I'm just starting out a new repository and etc... yeah I might dork that up... but the actual consequences from it are near 0.
  • 2
    @N00bPancakes
    I think I've experienced the worst of it; I went on vacation and came back to find that everything has gone lord of the flies. They'd spent a week trying to figure out why the build server wasn't producing artifacts containing the new code and everything was failing.

    Turns out, someone in my absence had checked in a delete on gitignore, and then the next person checked in cached local build artifacts. This then resulted in propagating to the CI and the CI ended up with broken symbols in test so nothing moved forward. I wish they would have bothered me.
  • 1
    @SortOfTested yeah if you've got one new repo you just made dorked up ... whatever.

    Once it starts hitting other tools, time to call in the troops.
  • 0
    See people.

    See!!?

    DO YOU SEE!!!?
Add Comment