|
Top-level
 @darius I tend to put those longform descriptions in pull requests, but I see how it could be valuable to have them in the commit message. When you say ban "-m", surely you mean except for WIP/checkpoint commits that will be rebased/squashed later, right? 2 comments
 @darius @graue If you require merge commits, the description of the PR gets copied into the merge commit message. It’s another reason why I personally don’t understand the Rebase/Squash lifestyle: use merge commits and that PR description you put a lot of writing in on github gets nicely copied into your git history. (Plus then you can use tools like —first-parent with merge commits.) |
Gregory's Server
@graue yes, correct on -m.
What I like about having this in git is that it stores the important information in git rather than in github dot com