Hacker News Reader

Comment by Sujan | Hacker News Reader

Nice project.

Shame that the history of the maturity model looks like this: https://github.com/LappleApple/feedmereadmes/commits/master/... Even when editing in the web UI you can - and should - set a commit message so one can actually understand how a document evolved without going through the diffs.

View on HN

Next Up: Git Commit Maturity Model

A level five commit is product-oriented, contains a vision statement for the change, has its own slogan and is updated at weekly or even daily intervals, so inaccuracies are unlikely.

You surpassed my level of snark and reached limits I considered unachievable. Well done!

How to write a great git commit message: http://github.com/joelparkerhenderson/git_commit_message

My personal favorites on the topic:

http://tbaggery.com/2008/04/19/a-note-about-git-commit-messa...

https://robots.thoughtbot.com/5-useful-tips-for-a-better-com...

Thanks! I added your links to the README.

The Wine project has been my go-to reference for what commits should look like in a large and complex project:

https://github.com/wine-mirror/wine/commits/master

During the short time I contributed to Wine, I really got to appreciate their high quality source control discipline.

I really like the "module: thing that changed" format for the title. We've been using that where I work. It helps keep commits focused and makes it much easier to read the log.

Reply on news.ycombinator.com