User:Evilpie/commit-restrictions: Difference between revisions

Jump to navigation Jump to search
Line 8: Line 8:


An example for a passing commit message would be,
An example for a passing commit message would be,
 
<pre>Bug 577872 - Create WebM versions of Ogg reftests. r=kinetik</pre>
    Bug 577872 - Create WebM versions of Ogg reftests. r=kinetik
 
notice the Bug ##### and the r=. Also the review is not checked at the moment, it could be at a
notice the Bug ##### and the r=. Also the review is not checked at the moment, it could be at a
feature point and it's strongly encouraged to have it. (please no "my-dog" or "burning").
feature point and it's strongly encouraged to have it. (please no "my-dog" or "burning").
Line 19: Line 17:
* Commit messages containing "bug" or "b=" followed by a bug number
* Commit messages containing "bug" or "b=" followed by a bug number
* Commit messages containing "no bug" (please use this sparingly)
* Commit messages containing "no bug" (please use this sparingly)
* Commit message indicates backout of a given 12+ digit changeset id, by starting with
* Commit message indicates backout of a given 12+ digit changeset id, by starting with (back out|backing out|backed out|backout)( of)? (rev|changeset|cset)s? [0-9a-f]{12}
 
  (back out|backing out|backed out|backout)( of)? (rev|changeset|cset)s? [0-9a-f]{12}
* Commit message starts with "merge" or "merging" and is actually a merge changeset.
* Commit message starts with "merge" or "merging" and is actually a merge changeset.


Line 35: Line 31:
Explicitly disallowed:
Explicitly disallowed:
* Commit messages containing "try: " to avoid unintentional commits that were meant for the try
* Commit messages containing "try: " to avoid unintentional commits that were meant for the try
  server.
  server.


All this is case case-insensitive.
All this is case case-insensitive.
Confirmed users
149

edits

Navigation menu