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
-`body`: Concise and actionable description of the violation and fix, following the below Comment Format
249
216
6.**Each comment must reference exactly one Rule ID.**
250
217
7.**Output must consist exclusively of calls to mcp__github_inline_comment__create_inline_comment in the required format.** No other text, Markdown, or prose is allowed.
251
-
8.**If no violations are found, create a comment** (with no quotes, markdown, or additional text):
252
-
LGTM 👍 Thank you for your hard work!
253
-
9.**Output LGTM if and only if**:
218
+
8.**If no violations are found, add a reaction to the PR**:
219
+
Add a 👍 (+1) reaction to the PR using the `addPrReaction` script (available in PATH from `.claude/scripts/`). The script takes ONLY the PR number as argument - it always adds a "+1" reaction, so do NOT pass any reaction type or emoji.
220
+
9.**Add reaction if and only if**:
254
221
- You examined EVERY changed line in EVERY changed file (via diff + targeted grep/read)
255
222
- You checked EVERY changed file against ALL rules
256
223
- You found ZERO violations matching the exact rule criteria
257
224
- You verified no false negatives by checking each rule systematically
258
-
If you found even ONE violation or have ANY uncertainty do NOT create LGTM comment - create inline comments instead.
225
+
If you found even ONE violation or have ANY uncertainty do NOT add the reaction - create inline comments instead.
259
226
10.**DO NOT invent new rules, stylistic preferences, or commentary outside the listed rules.**
260
227
11.**DO NOT describe what you are doing, create comments with a summary, explanations, extra content, comments on rules that are NOT violated or ANYTHING ELSE.**
261
-
Only inline comments regarding rules violations or general comment with LGTM message are allowed.
228
+
Only inline comments regarding rules violations are allowed. If no violations are found, add a reaction instead of creating any comment.
262
229
EXCEPTION: If you believe something MIGHT be a Rule violation but are uncertain, err on the side of creating an inline comment with your concern rather than skipping it.
Copy file name to clipboardExpand all lines: .github/ISSUE_TEMPLATE/DesignDoc.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,8 +14,9 @@ labels: Daily, NewFeature
14
14
-[ ] Email `strategy@expensify.com` and paste in the Proposal
15
15
-[ ] Fill out the **High-level overview of the problem**, **Timeline**, and **Terminology** sections of the Design Doc
16
16
-[ ] Email `strategy@expensify.com` (continue the same email chain as before) with the link to your Design Doc
17
-
-[ ] Host a **pre-design** meeting ([example](https://expensify.slack.com/archives/C01GTK53T8Q/p1665794669539419)) in `#expensify-open-source` to discuss any necessary details in public before filling out the **High-level of proposed solution** section.
17
+
-[ ] Host a **pre-design** meeting ([example](https://expensify.slack.com/archives/C01GTK53T8Q/p1665794669539419)) in `#expensify-open-source` to discuss any necessary details in public before filling out the **High-level of proposed solution** section
18
18
-[ ] Fill out the **High-level of proposed solution** section
19
+
-[ ] Ensure all employees have permission to comment and edit using `Share > Expensify, Inc > Commenter`
19
20
-[ ] Email `stategy@expensify.com` again with links to the doc and pre-design conversation in Slack
20
21
-[ ] Add the `DesignDocReview` label to get the **High-level of proposed solution** section reviewed
21
22
-[ ] Respond to any questions or concerns and bring up blockers in Slack to get a consensus if necessary
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+1-9Lines changed: 1 addition & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,7 +85,6 @@ This is a checklist for PR authors. Please make sure to complete all tasks and c
85
85
-[ ] iOS: Native
86
86
-[ ] iOS: mWeb Safari
87
87
-[ ] MacOS: Chrome / Safari
88
-
-[ ] MacOS: Desktop
89
88
-[ ] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
90
89
-[ ] I verified there are no new alerts related to the `canBeMissing` param for `useOnyx`
91
90
-[ ] I followed proper code patterns (see [Reviewing the code](https://github.com/Expensify/App/blob/main/contributingGuides/PR_REVIEW_GUIDELINES.md#reviewing-the-code))
@@ -157,11 +156,4 @@ This is a checklist for PR authors. Please make sure to complete all tasks and c
0 commit comments