39
Knossos
8y

I tell a colleague, "Hey, could you make your commits more meaningful? A commit message of '.' helps nobody.".

He then uses 'no message' for his commits.

Also, commits every 30 seconds. I know commit often... But is that really necessary?

Why.

Comments
  • 4
    Commit on every small milestone is fine. Commit on every tiny detail is not. No explanation of commit is double not okay.
  • 1
    You should teach him difference between saving his work and git commit
  • 1
    Sounds like a nice way to break the Repo. If you are ever in a bad mood just push a big commit at the same time has him and teach him a valuable lesson.
  • 0
    @crani and then he forces his changes. Maybe not the best way...
  • 2
    I've had to commit every time I changed something because the machine I was developing in was different than the one I was testing on. Pushing and pulling with git was the fastest way to transfer the latest versions.
  • 2
    Seems like someone needs to...*clears throat and puts on shades*...git good
  • 1
    @nblackburn 👉😎👉
Add Comment