14
octoxan
6y

Trying to pick through a recently ex-coworkers project repository... these forking commits!

Favorite might be "That was gonna mess up". So why did you commit it?

At first I was mad, but by the bottom two I was dying laughing.

I'll save you from typing out the link:
https://media1.giphy.com/media/...

Comments
  • 3
    He still doesn't know what that first one does. (It breaks everything)
  • 2
    @xewl Haha right! It was actually just him adding !important to like 100+ lines of CSS.
  • 2
    And he couldn't test that offline, before committing???

    !important Should be banned anyway. If you need to use that, something's probably wrong with the logic above or around it.. :/
  • 1
    @xewl One of the many reasons I'm glad he's gone. Don't commit something that isn't working. He even had a local copy of the site running in Vagrant so yeah beats me.
  • 0
    @octoxan "Yeah, I'll commit my CSS changes, otherwise my vagrant box won't know about the change"

    Gu'uhdbyeee!
  • 2
    @jschmold He actually left development entirely now lol
  • 1
  • 0
    @Clear0Ff I posted the link in the post also =]
  • 1
    @octoxan fk , im blind

    sorry xD
  • 0
    I once had a similar line of ~5-10 commits for a "only happens in production" type of bug in a fully automatically deployed site.

    No fun to find those commits and even less to write them.
Add Comment