I'm not sure how I feel about the present-tense dictum. When I commit frequently most of my commit messages end up in present tense anyway, but sometimes they don't, and it all still reads pretty well. I think the emphasis should be on frequent commits which keep the narrative of a codebase coherent and chugging along.<p>Here's an example changelog: <a href="http://github.com/akkartik/wart/commits/unstable" rel="nofollow">http://github.com/akkartik/wart/commits/unstable</a>. Criticisms?
is it just me, or does anyone else think that though the design is prettier, it kinda makes other parts of the app look bad - for instance compare the commit style to the tree listings. it's not that one or the other look bad, it's just the dissimilarity is jarring.
GitHub is doing a fantastic job of building a consistent presence from top to bottom. The changes as a whole have been extremely impressive over the past few months. I, as a designer that uses GitHub on a daily basis at work, am very enthusiastic about the latest updates, the new commit styles included. The GitHub team has been extremely quick to iterate and launch updates recently. I'm sure there's plenty more to come.