I have been using Git a long, long time. I have worked on Git clients and libraries. At some places I've worked, I am the person folks go to when they need Git help.

And yet, only today I learned you can pass -m to commit twice (or more) and it will do the right thing of making each successive message a new paragraph (which is useful for the convention of a short summary as a single first line and following paragraphs as a more detailed message).

@halfogre oh interesting. Does it correctly format the paragraphs to the right number of columns if you do it this way? I hate going in to an editor to write my commit messages but judging line length from the command prompt is a PITA.

@megmac
I used to use -m flags but eventually switched to using an editor.

Why? Because most of my projects are solo and I don't want to use an issue tracker. Instead I prefer to provide the context right next to the changes. Using an editor makes me use the description field, too.

It's a bummer that GitHub throws away most of the conversation in a PR unless you remember to update the first message before merging.

You see, I want to keep the information offline (because Germany).

@halfogre

@megmac
That being said, combing through the documentation I can see that there are many gems most of us will never use.

I'd pick up a good book to learn some of them (most likely always behind the curve, but that doesn't matter much)

@halfogre