MediaMetz/gemini-cli
1
0
Fork 0
mirror of https://github.com/google-gemini/gemini-cli.git synced 2026-05-15 14:23:02 -07:00
Code Issues Packages Projects Releases Wiki Activity

docs(skills): add key model and diff/edit functionalities to maintainer-only criteria

Browse Source
This commit is contained in:
Coco Sheng
2026-04-08 16:06:17 -04:00
parent a7ee67c177
commit 3c7203f79e
1 changed files with 4 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/core/src/skills/builtin/github-issue-triage/references/triage_rules.md
+4 -1
View File
@@ -115,8 +115,11 @@ Search for duplicates using `gh issue list --search "<keywords>" --repo <owner/r
## Step 6: Triage Summary
Review the issue comments to see if a community member has already identified the root cause.
- If a root cause is identified: determine if it is a very simple fix. If it is a simple fix, post guidance for the fix, categorize the issue as **Maintainer-only**, and explain why. If it is not a simple fix, determine whether it should be **Maintainer-only** or **Help-wanted** and explain why.
- If no root cause is identified: State whether the issue should be categorized as **Maintainer-only** (epic, core architecture, sensitive fixes, internal tasks, issues requiring deep investigation, changes to key UI/UX that affect all users, modifications to core internal data structures and IPC mechanisms, or changes to token/billing logic and key model functionalities) or **Help-wanted** (small well-defined features, easy-to-fix bugs, good for community, or tasks ready for external help). Your comment should be brief and clearly explain *why* it fits that category.
- If no root cause is identified: State whether the issue should be categorized as **Maintainer-only** (epic, core architecture, sensitive fixes, internal tasks, issues requiring deep investigation, changes to key UI/UX that affect all users, modifications to core internal data structures and IPC mechanisms, changes to token/billing logic, or changes to key model and diff/edit functionalities) or **Help-wanted** (small well-defined features, easy-to-fix bugs, good for community, or tasks ready for external help). Your comment should be brief and clearly explain *why* it fits that category.
- If you categorized the issue as **Help-wanted**, also run `gh issue edit <issue_url> --remove-label "status/need-triage" --add-label "help wanted"`.
- If you categorized the issue as **Maintainer-only**, also run `gh issue edit <issue_url> --remove-label "status/need-triage" --add-label "🔒 maintainer only"`.
- Action: `gh issue comment <issue_url> --body "### Triage Summary\n\n<your summary>"`
- **STOP EXECUTION**.
`
- **STOP EXECUTION**.
ION**.