Confirmed users
149
edits
User:Evilpie/commit-restrictions: Difference between revisions
→Commit Message Restrictions
| Line 17: | Line 17: | ||
Allowed are: | Allowed are: | ||
* Commit messages containing "bug" or "b=" followed by a bug number | |||
* Commit messages containing "no bug" (please use this sparingly) | |||
* Commit message indicates backout of a given 12+ digit changeset id, by starting with | |||
<pre>(back out|backing out|backed out|backout)( of)? (rev|changeset|cset)s? [0-9a-f]{12}</pre> | |||
* Commit message starts with "merge" or "merging" and is actually a merge changeset. | |||
Special exceptions: | Special exceptions: | ||
* Upadting the NanoJit import in the js/src tree ("Update nanojit-import-rev stamp.") | |||
* Commits by User is "ffxbld", "seabld", "tbirdbld", or "cltbld". | |||
* When the commit is older then some date shortly after the hook has been enabled to allow merges | |||
from other branches. This exception will be lifted after a short period of time | |||
(propably a few months) after the hooks was enabled | |||
* You can also specify "ALLOW BAD COMMIT MESSAGES" in the tip (latest) commit message to override | |||
all the restrictions. This is ultra cruel, you should only do this if you have a verry good reason. | |||
Explicitly disallowed: | Explicitly disallowed: | ||
* Commit messages containing "try: " to avoid unintentional commits that were meant for the try | |||
server. | |||
All this is case case-insensitive. | All this is case case-insensitive. | ||
| Line 41: | Line 41: | ||
http://hg.mozilla.org/hgcustom/hghooks/file/xxxxx/mozhghooks/xxxxxx.py. | http://hg.mozilla.org/hgcustom/hghooks/file/xxxxx/mozhghooks/xxxxxx.py. | ||
=== Local setup === | |||
It is also possible to use this hook locally so you can already see if there is something wrong | It is also possible to use this hook locally so you can already see if there is something wrong | ||