You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,8 @@ Need for Call for Review:
9
9
<< check [Process Document on Call for Review](https://act-rules.github.io/pages/design/process/#call-for-review) >>
10
10
This can be merged with 1 approval << choose reason: editorial changes to website/test code, adding new contributor, other (explain). >>
11
11
This will not require a Call for Review << choose reason(s): editorial changes (including to the applicability, expectation or examples section), changes to assumptions, background, accessibility support, change to website/test code (not rule), other (explain). >>
12
-
This will require a 1 week Call for Review << small changes affecting a small number of test cases, if in doubt do not use this. >>
13
-
This will require a 2 weeks Call for Review << new rule, or substantial changes affecting a large number of test cases, if in doubt, use this. >>
12
+
This will require a 1 week Call for Review << small changes affecting a small number of examples, if in doubt do not use this. >>
13
+
This will require a 2 weeks Call for Review << new rule, or substantial changes affecting a large number of examples, if in doubt, use this. >>
Copy file name to clipboardExpand all lines: __deprecated__/pages/contribute/rule-feedback.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ To start giving feedback and doing reviews for draft rules:
41
41
42
42
We also welcome any feedback and suggestions for changes to already published rules. The published rules should be as precise as possible, limiting the number of potential false positives and false negatives. For this, it is important to draw on as many tool and methodology implementations and expert opinions as possible.
43
43
44
-
Feedback and corrections for existing rules can target any of the sections of the rule itself (Applicability, Expectations, Accessibility Support, etc.), as well as the test cases, for example to expand the edge case coverage.
44
+
Feedback and corrections for existing rules can target any of the sections of the rule itself (Applicability, Expectations, Accessibility Support, etc.), as well as the examples, for instance to expand the edge case coverage.
45
45
46
46
You have several options for correcting existing rules:
0 commit comments