Closed
Bug 1108755
Opened 10 years ago
Closed 10 years ago
git commit message linter for the pre-commit hook
Categories
(Input Graveyard :: Code Quality, defect)
Input Graveyard
Code Quality
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: willkg, Assigned: lgp171188, Mentored)
Details
(Whiteboard: u=dev c=codequality p= s=input.2014q4)
I have a lot of anxiety about getting bug numbers in commit messages right. Today I flubbed one. That's kind of annoying and makes future archaeology harder.
I think it might be nice for a git commit message linter. Something that does the following:
1. verifies the summary line has bug numbers in the right format
2. does a bz lookup, prints out the bug numbers and the bug summaries so you can verify correctness
3. enforces max 79-chars-per-line
This would be helpful.
|
Reporter | |
Comment 1•10 years ago
|
||
In a PR: https://github.com/mozilla/fjord/pull/422
Landed in master: https://github.com/mozilla/fjord/commit/a36a2319890cf6309969e2a956524c11635afba9
Assignee: nobody → lgp171188
Mentor: willkg
|
|
Reporter | |
Comment 2•10 years ago
|
||
This doesn't need to be deployed, so I'm marking it FIXED.
Thank you!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Whiteboard: u=dev c=codequality p= s=input.2015q1 → u=dev c=codequality p= s=input.2014q4
|
||
Updated•8 years ago
|
Product: Input → Input Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•