News for hackers. Stuff that matters.
Re:How to Write a Git Commit Message by nirvdrum on Sunday September 13, 2015 @07:25PM (#10213111)
A lot of people do something similar on GitHub. If you're going to do this, please include the issue subject in the commit message somewhere. "Fixes #135" is absolutely meaningless outside the context of whatever tool. And it absolutely falls apart if the project lives long enough to change issue trackers.
Re:How to Write a Git Commit Message by fenomas on Sunday September 13, 2015 @11:25PM (#10213536)
Much agreed. "Fixes #123" makes sense for pull request messages, but the commit messages should be verbose!