I generally like to separate changes into as many commits as is reasonable. That way I can go back and see how, why, when and what was changed, along with meaningful commit messages.

But sometimes...
Git add *
Git commit -m "changed lots of stuff"

God I hate myself.

  • 4
    I had 484 changed files that I commited before going on holiday with some generic message (took over an hour to commit them all) came back from 3 days off to them all being merged. Still picking up the pieces now as the only testing I'd done was did it compile
  • 2
    @njpugh90 ahh the good ol "I'm sure it won't segfault. After all, gcc compiled fine."
  • 1
    Just like any other dev
  • 2
    @deadPix3l yeah I had that lol
    Tracking down float to long double conversion issues right now :(
  • 1
    git commit -a is a lazy dev's best friend.
Add Comment