Skip to content
Browse files
Adding details about links
  • Loading branch information
David Jarvis committed Feb 19, 2016
1 parent 788183c commit 6cd27e3e0486ae2bae6a1a583c9759efef48a727
Showing with 7 additions and 2 deletions.
  1. +7 −2
@@ -13,5 +13,10 @@ issues or PRs that simply don't fit our internal engineering needs.
PRs to the style guide should include a description of the proposal, including
examples of what "good" and "bad" code would look like under the new rule, as
well as a rationale for the rule in question. The description of the rule and
the examples belong in ``; the rationale goes in the corresponding
section in ``
the examples belong in ``. If the rationale is anything other than "for
consistency", it should go into a corresponding section in ``.
Style rules that are purely about consistency do not need rationales.

Individual rules should include, after the description of the rule, a link to
that rule, and, if a rationale is being added to ``, a link to the
detailed rationale.

0 comments on commit 6cd27e3

Please sign in to comment.