News for hackers. Stuff that matters.
Re:How to Write a Git Commit Message by jph on Sunday September 13, 2015 @06:02PM (#10212946)
We advocate also using hashtags and URLs in the commit message body.

Our hashtags correspond to specific areas such as #analytics, #localization, #api. These hashtags are easily searchable by the respective teams, and we also use simple shell scripts that categorize by tag, e.g. "List all the changes related to #analytics".

Our URLs link to the corresponding tasks in Asana, Jira, etc., and also to any relevant background information such as RFCs, ISO standards, NIST docs, etc.

Re:How to Write a Git Commit Message by agumonkey on Sunday September 13, 2015 @10:40PM (#10213467)
Saw this blog last week : http://ericjmritz.name/2015/05/27/my-global-git-commit-templ...

He uses a template with a few metadata, and tags too. In an older entry he mentions using a special WIP tag for successive sequences of iterative changes toward a fix too.

Re:How to Write a Git Commit Message by jarfil on Monday September 14, 2015 @10:43AM (#10215292)
Isn't WIP what branches are for?
Re:How to Write a Git Commit Message by agumonkey on Monday September 14, 2015 @03:32PM (#10216971)
I guess I don't branch enough then.
Re:How to Write a Git Commit Message by bobwaycott on Sunday September 13, 2015 @06:36PM (#10213015)
This is a pretty clever idea. I might start playing around with this in my own projects. Thanks for the idea!
Re:How to Write a Git Commit Message by bdg on Sunday September 13, 2015 @07:30PM (#10213120)
I see this done from time to time as [feature] also.