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
- Post comments for EVERY significant issue you find (not just a summary)
131
+
- Keep the body text concise and use \n for line breaks within the body parameter
135
132
136
133
**Inline Comment Format:**
137
134
- Use emoji severity: 🔴 Critical | 🟡 Important | 🔵 Consider
@@ -142,14 +139,11 @@ jobs:
142
139
143
140
**Example:**
144
141
```
145
-
🔴 **[Security]**: Potential SQL injection vulnerability. User input is concatenated directly into SQL query.
146
-
147
-
**Fix:** Use parameterized queries:
148
-
\`\`\`typescript
149
-
const result = await query('SELECT * FROM users WHERE name = $1', [userName]);
150
-
\`\`\`
142
+
🔴 **[Security]**: Potential SQL injection vulnerability. User input is concatenated directly into SQL query.\n\n**Fix:** Use parameterized queries:\n\`\`\`typescript\nconst result = await query('SELECT * FROM users WHERE name = $1', [userName]);\n\`\`\`
151
143
```
152
144
145
+
Note: In the actual gh command, newlines are represented as \n within the body parameter.
146
+
153
147
### Step 4: Post Summary Comment
154
148
After posting inline comments, create a summary with:
0 commit comments