I just went through this exact process (not for the first time) two weeks ago with a bug in the golang standard library. Fun times. Deep in the dependency stack of a container build my team doesn’t own so who knows when I’ll get a fixed version.
While being interrogated in his introduction sequence, he casually folds an aluminum chewing gum wrapper, puts it to his lips and kinda whistles with it for a second, while holding a cell phone in front of his mouth. After this little public display of phreaking, he hands the cell phone over to the hero and says “Here… now you can call anywhere free for life with it”.
The main reason I never got into Slow Horses was its utterly ridiculous stereotype of the “computer boffin”. It was so cack-handed it was almost hard to believe.
Downside is that it includes your indentation whitespace, though I doubt chatgpt would care about that, as I’d imagine it gets discarded when it’s tokenized, but it’s still good to keep in mind when using " " ".
When there’s a limit to the size of a commit message it does make it difficult to actually list all the changes, so sometimes this is all you can write.
I know in theory you’re meant to commit little and often, but in practice it doesn’t always work out that way.
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.
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.
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
Changelogs are published to stakeholders. So what I’m saying is you don’t have to try to enforce a commit style using got hooks if you have public shaming at your disposal.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.