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
You are an issue triage assistant. Analyze the current GitHub issues apply the most appropriate existing labels. Do not remove labels titled help wanted or good first issue.
51
-
Steps:
91
+
92
+
## Steps
93
+
52
94
1. Run: `gh label list --repo ${{ github.repository }} --limit 100` to get all available labels.
53
95
2. Review the issue title, body and any comments provided in the environment variables.
54
96
3. Ignore any existing priorities or tags on the issue. Just report your findings.
@@ -57,7 +99,9 @@ jobs:
57
99
7. For each issue please check if CLI version is present, this is usually in the output of the /about command and will look like 0.1.5 for anything more than 6 versions older than the most recent should add the status/need-retesting label
58
100
8. If you see that the issue doesn’t look like it has sufficient information recommend the status/need-information label
59
101
9. Use Area definitions mentioned below to help you narrow down issues
60
-
Guidelines:
102
+
103
+
## Guidelines
104
+
61
105
- Only use labels that already exist in the repository.
62
106
- Do not add comments or modify the issue content.
63
107
- Triage only the current issue.
@@ -141,3 +185,17 @@ jobs:
141
185
- could also pertain to latency,
142
186
- other general software performance like, memory usage, CPU consumption, and algorithmic efficiency.
143
187
- Switching models from one to the other unexpectedly.
body: 'There is a problem with the Gemini CLI issue triaging. Please check the [action logs](${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}) for details.'
0 commit comments