22

Why do people fucking do this? You're working in a team, ffs. Even if right now you're the only one working on that branch or whatever, that doesn't make it okay to have the most useless commit messages of all time.

Comments
  • 14
    Because he/she uses git for cloud storage, not vcs.
  • 3
    When a commit message is required
  • 3
    Merge -> squash and delete branch!
  • 2
    I use Git only for myself, and most of my commit messages are something like "much wow, many refactor"
  • 0
    1
    1
    1
    1
  • 0
    Yeah i usually save it as 'updated' then commit
  • 5
    @C0D4 dont merge, delete branch
  • 4
    It's probably compressed and in binary. You'll need to read millions or billions of more commits until it all makes sense.
  • 0
    @irene Yeah, I'm still waiting for that moment... Luckily I can view the diff for each commit, but that's slower
  • 2
    We have a commit message policy in the company I work to prevent something like this.
  • 1
    On MY branch I often commit WIP, until a functional military stone where I squash it to have a true commit message.
    Also use it when I couldn't finish a task the same day. Or when I config/debug a CI workflow problem as it must go through the CI.

    The problem is more : why the commit messages made it into master!
  • 4
    If a person cant even write a decent commit message, i wouldnt trust their skills in writting code.
  • 0
    minor

    minor

    minor

    bugfix

    minor
  • 0
    I do that (not at such gruesome levels tho) because I know I gonna rebase my commits, and the changes are so minuscule that they don't deserve a comment.
    Something like
    -m "optimized"
    -m "s" #for "same"
    -m "s"
    Then just one commit named "optimizations"
  • 1
  • 0
    @p3rand0r still optimizations is saying the same as just commenting 1.
Add Comment