4 ms·

I think this needs a little more human curation. There are too many commit messages that are about internals that users really don't want to know about. Here's

by dreeves 15y ago

I think this needs a little more human curation. There are too many commit messages that are about internals that users really don't want to know about. Here's what we do: http://blog.beeminder.com/blogdog http://blog.beeminder.com/blogdog In short, we have a special twitter account for User-Visible Improvements (UVIs). We manually look over our commits and task list and tweet on average one UVI per day. EDIT: Also, thanks for making -M availaible! I'm trying it out.

tikhonj 15y ago
As another option, couldn't you just include some sort of tag in each commit you want included, when you commit it? Something like "#interesting" at the end of the message. I'm not sure that would be better, but it would be a nice option to consider.
deleted 15y ago
[deleted]
jpadilla_ 15y ago
That's very interesting! We've been discussing a couple of ways "curating" those commit messages. One way I've thought of doing is to take the commit messages with the highest impact(according to Github: Impact is lines added + lines deleted), still not sure about it. Thanks for the feedback!
roryokane 15y ago
One way -M could automate user-visible and non-user-visible improvements is to have separate branches for each type of improvement. -M would email only commits in the UVIs branch. (And the master branch would just merge commits from those two separate branches, and contain no original commits.) This would allow UVIs to be chosen at commit-time, rather than manually right before sending the email. (It would be possible but harder to choose UVIs manually right before sending the email, by editing history so those commits were in the right branch.)