Skip to content

ci: add gemini bot for issue triage#2032

Open
Yuan325 wants to merge 2 commits intomainfrom
issue-triage
Open

ci: add gemini bot for issue triage#2032
Yuan325 wants to merge 2 commits intomainfrom
issue-triage

Conversation

@Yuan325
Copy link
Copy Markdown
Contributor

@Yuan325 Yuan325 commented Nov 25, 2025

Description

Added issue triage workflows. Consolidated the automated and scheduled issue triage workflow from gemini-cli repo.

The workflow will be triggered with the following:

  • Daily at 9am - will catch any issues that are missed, or issues with the need-triage label.
  • Whenever there's a new issue opened (reopen does not trigger this workflow)
  • manually dispatch

This workflow will do the following:

  • find any issues that needs to be triaged (including issues without any labels, or issues with the need-triage label).
  • for each issue, the bot will determine the product: label, type: label, and priority: label that best matches the issue.
  • if issue doesn't have sufficient information, it will leave a comment to request for relevant information.
  • If any issues is identify as priority: p0 label, it will add a status: manual-triage label with a note so that maintainer can manually check those issues.
  • If the bot are not able to identify the priority: label, it will also apply the status: manual-triage label.
  • after adding labels, it will remove the status: need-triage label.
  • blunderbuss will assign the PR based on product: label (if set by the bot).

With this, this PR added a couple of labels:

  • status: need-triage -- maintainer can add this label to get the issue triaged by the automation.
  • status: manual triage -- triage automation will add this label if the issue needs to get triaged manually.

This PR also updated docs to CONTRIBUTING.md for new sources to add their labels.

@Yuan325 Yuan325 requested a review from a team November 25, 2025 07:39
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Warning

You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again!

@Yuan325
Copy link
Copy Markdown
Contributor Author

Yuan325 commented Dec 18, 2025

@averikitsch what do you think about adding both the automated and schedule? Or should we start with the automated for now? (removing the scheduled workflow) to keep it simpler.

@Yuan325 Yuan325 marked this pull request as ready for review December 18, 2025 19:15
REPOSITORY: '${{ github.repository }}'
AVAILABLE_LABELS: '${{ steps.get_labels.outputs.available_labels }}'
with:
gcp_workload_identity_provider: '${{ vars.GCP_WIF_PROVIDER }}'
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we setting this up?

@Yuan325 Yuan325 added priority: p2 Moderately-important priority. Fix may not be included in next release. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. and removed priority: p2 Moderately-important priority. Fix may not be included in next release. labels Dec 31, 2025
@Yuan325
Copy link
Copy Markdown
Contributor Author

Yuan325 commented Jan 6, 2026

currently setting up vars and secrets for this.

@Yuan325 Yuan325 added the do not merge Indicates a pull request not ready for merge, due to either quality or timing. label Jan 6, 2026
let parsedLabels;

try {
const jsonMatch = rawLabels.match(/```json\s*([\s\S]*?)\s*```/);
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be rawOutput.match() instead?

echo "📅 Bulk Mode: Running full triage scan..."
echo '🔍 Finding issues without labels...'
NO_LABEL_ISSUES="$(gh issue list --repo "${GITHUB_REPOSITORY}" \
--search 'is:open is:issue no:label' --json number,title,body)"
Copy link
Copy Markdown
Contributor

@dishaprakash dishaprakash Jan 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we make this search more specific to find issues which do not have a priority / triage label?
Edge case - Would it fail in the scenario that a new issue is opened and the author adds a bug / question / etc. tag?

@Yuan325 Yuan325 added priority: p2 Moderately-important priority. Fix may not be included in next release. and removed priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Mar 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do not merge Indicates a pull request not ready for merge, due to either quality or timing. priority: p2 Moderately-important priority. Fix may not be included in next release.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants