{"action":"closed","issue":{"url":"https://api.github.com/repos/pravj/termping/issues/1","labels_url":"https://api.github.com/repos/pravj/termping/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/pravj/termping/issues/1/comments","events_url":"https://api.github.com/repos/pravj/termping/issues/1/events","html_url":"https://github.com/pravj/termping/issues/1","id":38832136,"number":1,"title":"Wrong use of prefixes in commit messages","user":{"login":"captn3m0","id":584253,"avatar_url":"https://avatars.githubusercontent.com/u/584253?v=3","gravatar_id":"","url":"https://api.github.com/users/captn3m0","html_url":"https://github.com/captn3m0","followers_url":"https://api.github.com/users/captn3m0/followers","following_url":"https://api.github.com/users/captn3m0/following{/other_user}","gists_url":"https://api.github.com/users/captn3m0/gists{/gist_id}","starred_url":"https://api.github.com/users/captn3m0/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/captn3m0/subscriptions","organizations_url":"https://api.github.com/users/captn3m0/orgs","repos_url":"https://api.github.com/users/captn3m0/repos","events_url":"https://api.github.com/users/captn3m0/events{/privacy}","received_events_url":"https://api.github.com/users/captn3m0/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2014-07-27T04:23:28Z","updated_at":"2015-02-09T21:02:43Z","closed_at":"2015-02-09T21:02:43Z","body":"I read your commit log, and the blog post, and just thought I should correct you on the usage of commit prefixes. Using commit prefixes can be good (I've recently started using them). Here's a screenshot of the commit prefixes I've been using: \r\n\r\n![image](https://cloud.githubusercontent.com/assets/584253/3712984/fc4d9392-1544-11e4-885e-ce3bfaaa6843.png)\r\n\r\nHowever, the prefixes that you use are: `add, remove, change, fix, update`. While these may make some sense in a small repo like yours; they are not all good prefixes (fix might be fine). A good commit prefix tells you *what the commit changed*, instead of *how it was changed*. \r\n\r\nKnowing that the commit involved addition or removal of 5 lines is meaningless. What's more important is that it involved changing the PHYSICS code, or perhaps it was a REFACTOR, changing none of the functionality.\r\n\r\nMy current usage of prefixes is to indicate which MODULE the code worked on. This is similar to how the [linux kernel uses prefixes](https://github.com/torvalds/linux/commits/master).\r\n\r\ntermping is awesome. :+1: "}}