Closed
Bug 660705
Opened 14 years ago
Closed 14 years ago
Push hook to prevent accidentally pushing without a bug number
Categories
(Developer Services :: Mercurial: hg.mozilla.org, enhancement)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 506949
People
(Reporter: jruderman, Unassigned)
Details
Commits without bug numbers mess with regression hunting, regression filing, backouts, and patch attribution.
I also rely on being able to get a list of bugs from hg, in order to write The Burning Edge, identify fixes that need fuzzing or security review, and identify fixes that need Feature Pages.
Allow commits (on mozilla-central and feeder branches) only if they:
* Have "bug" or "b=" followed by a bug number
* Have "no bug"
* Start with
(back out|backing out|backed out|backout)( rev| changeset|)? [0-9a-f]{12}
* Start with "merge"
* Come from user "ffxbld"
These rules should apply to all commits (not just heads), but should be relaxed for commits that come along with merges, so the first merge from a project branch doesn't get rejected.
Might be able to borrow code from bug 659380.
Reporter | ||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Assignee | ||
Updated•10 years ago
|
Product: Release Engineering → Developer Services
You need to log in
before you can comment on or make changes to this bug.
Description
•