{"comment":{"url":"https://api.github.com/repos/MTG/freesound/comments/11675854","html_url":"https://github.com/MTG/freesound/commit/c97a9f420660187570e154c5d4fb79fbceeb49b6#commitcomment-11675854","id":11675854,"user":{"login":"alastair","id":19217,"avatar_url":"https://avatars.githubusercontent.com/u/19217?v=3","gravatar_id":"","url":"https://api.github.com/users/alastair","html_url":"https://github.com/alastair","followers_url":"https://api.github.com/users/alastair/followers","following_url":"https://api.github.com/users/alastair/following{/other_user}","gists_url":"https://api.github.com/users/alastair/gists{/gist_id}","starred_url":"https://api.github.com/users/alastair/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alastair/subscriptions","organizations_url":"https://api.github.com/users/alastair/orgs","repos_url":"https://api.github.com/users/alastair/repos","events_url":"https://api.github.com/users/alastair/events{/privacy}","received_events_url":"https://api.github.com/users/alastair/received_events","type":"User","site_admin":false},"position":null,"line":null,"path":"","commit_id":"c97a9f420660187570e154c5d4fb79fbceeb49b6","created_at":"2015-06-15T09:03:02Z","updated_at":"2015-06-15T09:03:02Z","body":"A nicer commit message would briefly explain what the bug was (instead of just saying 'fixed a bug') so that you can see what has changed by looking at log messages instead of having to read the diff. There are lots of blog posts about good commit messages - some of them I don't agree with. Here's an example of one that seems reasonable: https://github.com/erlang/otp/wiki/Writing-good-commit-messages"}}