these are great. Any tips on how to nudge someone in an open source project to adopt them?
Posted on by Michael Bishop
This may be the best guidance I've seen anywhere on writing a really good commit history. My ideal commit combines code changes, test changes, related documentation updates and some background info in the commit, plus a link to the issue tracker https://t.co/PhaxfB3Gx0
— Simon Willison (@simonw) January 13, 2018
At Eventbrite our code review proves helps here – changes are reviewed in phabricator before being merged as a single commit so feedback on the commit message text can be incorporated at review time – same thing could work for GitHub pull requests