Programmer Humor

19503 readers

358 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

[email protected]

425

git commit -m "minor fixes" +26858 -69429 (feddit.de)

submitted 9 months ago by [email protected] to c/[email protected]

69 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] PuzzledBlueberry 10 points 9 months ago (1 children)

Even if you have a big commit, you can always write something more descriptive than this. And commit messages can be huge, so the limit shouldn't be an excuse to write a useless message.

[–] [email protected] 9 points 9 months ago (1 children)

For those wondering how to exceed the 70 (80) recommended character limit and still follow best practices:

Write the title on the first line, keep below 70 characters.
Make two (2) newlines
Write one or more descriptive paragraphs.

The first line will be shown as commit message, and the full text can usually be viewed by checking out the commit. Sentences can span multiple lines, but try to keep the line length below 70 characters for best readability.

This off the top of my head, so feel free to correct me if I've misremembered the best practices.

[–] [email protected] 4 points 9 months ago

I generally write a single line summary and then a list of the specifics like:

Did stuff (except more detailed than that)
 - The first thing I did
  - Maybe some more detail about the first thing because there's a rationale to explain
 - The second thing I did
 - Third thing

Etc.