Learn More
Resend Email
6
rixcy
5y

If you ever wondered how to write a really bad commit message, here are some of my colleague's...

1. -
2. fixed conflict
3. initail push
4. css fix
5. amends to css
6. footer

And then a ton more hyphens. I wouldn't care as much if the code he wrote actually worked. But when it's down to his colleague's to fix his god awful code, it makes it a tad annoying trying to trawl through useless commit messages trying to find where he dun goofed. /rant

rant
Favorite
Ranter
Comments
  • 0
    5y
    I see this more then I like from colleagues: “fixes” 🤦‍♂️
  • 0
    5y
    My highlight is that every commit on frontend code is followed by a commit "lint..." bc our build server breaks the build on lint errors and locally you have to run the check by hand and everybody always forgets before pushing
  • 0
    5y
    7. Minor fixes
  • 0
    5y
    Corrected bug.

    Corrected bug introduced by fixing a bug.

    Work fucker.
  • 1
    5y
    @Katakompe maybe get git hooks?
  • 1
    5y
    @BoKKeR, we probably should.
    We could also add the lint check to the gradle build, butnsomehow nobody thought of that, or nobody wants to do this.
    Seems like the juniors got to fix things up again :D
  • 0
    5y
    Implement a structure, e.g. issue id, tags, short message describing what is done imperatively. Enforce that structure.

    Also:

    INITAIL!
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment