feat: improve gemini issue triage workflow #171
Conversation
jerop
force-pushed
the
feat/gemini-issue-triage-improvements
branch
5 times, most recently
from
0c4a4d2 to
c2eb38c
Compare
jerop
force-pushed
the
feat/gemini-issue-triage-improvements
branch
2 times, most recently
from
ebb153e to
7c76b68
Compare
There was a problem hiding this comment.
Perhaps a silly question, but is there a reason we don't use github.rest.issues.setLabels instead of bifurcating between "add" and "remove"? This only runs when issues are (re)opened, so I'm not sure we need to take on the additional complexity and API calls.
I only commented on the first file, but consider the feedback throughout all files.
jerop
force-pushed
the
feat/gemini-issue-triage-improvements
branch
5 times, most recently
from
2df9eb6 to
3916c88
Compare
This commit improves the gemini issue triage workflow by: - Passing the available labels as an environment variable to the Gemini CLI. - Using the output of the Gemini CLI to apply labels to the issue. - Adding a step to get all repository labels and pass them to the gemini-cli. - Updating the prompt to classify the issue and output the labels in JSON format. - Adding a step to apply the labels to the issue using the github-script.
jerop
force-pushed
the
feat/gemini-issue-triage-improvements
branch
from
3916c88 to
d5d2051
Compare
|
@sethvargo addressed all the feedback, thank you!
was originally taking a more conservative approach to add new labels and remove some but leave others untouched, but it seems too complex for little benefit, and the user can always implement this if needed -- so switched to the simpler approach using Example runs in a private repo I shared with you: |
## What's Changed * Highlight core tools and mcp servers in configuration docs by @jerop in #160 * feat(/review): support pull_request_review & pull_request_review_comment events by @leehagoodjames in #161 * Github-workflow to automate validation of new PRs based on Contribution Guidelines of the repository by @jasmeetsb in #162 * fix: Update gemini-issue-automated-triage.yml by @teolemon in #165 * Add instruction for code review limit. by @aliciatang07 in #168 * feat(logging): Enable debug logging across all workflows and gemini-cli by @leehagoodjames in #178 * feat(workflows): reduce restrictions for invoking workflows for private repos by @leehagoodjames in #177 * fix(runner): capture stderr and stdout after command finishes by @sethvargo in #183 * chore(logging): only enable Gemini debug when DEBUG is set by @sethvargo in #180 * feat: improve gemini issue triage workflow by @jerop in #171 ## New Contributors * @jasmeetsb made their first contribution in #162 * @teolemon made their first contribution in #165 **Full Changelog**: v0.1.10...v0.1.11
This commit improves the gemini issue triage workflow by: