Skip to content

build: added action to automatically triage issues#838

Merged
kikoso merged 10 commits intomainfrom
build/automatically-triage-issues
Feb 6, 2026
Merged

build: added action to automatically triage issues#838
kikoso merged 10 commits intomainfrom
build/automatically-triage-issues

Conversation

@kikoso
Copy link
Collaborator

@kikoso kikoso commented Feb 1, 2026

Summary

This PR introduces an automated triage system powered by the Gemini 2.5 Flash model. It automatically assesses the priority of new Issues and applies appropriate GitHub labels to streamline the project management process.

Changes

  • New Workflow: Added triage-issue.yml which triggers on Issue events (opened, edited) and workflow_dispatch.
  • Restricted Scope: Unlike previous iterations, this is now restricted to Issues only to keep PR workflows clean.
  • Triage Script: Added triage_issue.py to handle the interaction with the Gemini API using urllib.request (zero external dependencies).
  • Automated Labeling: The system is specifically optimized to detect and apply Priority labels:
    • Priority: priority: p0 (Critical) through priority: p4 (Low).
  • Security: Updated workflow permissions to minimal scope (issues: write, contents: read).

Setup Required

To enable this feature, a GEMINI_API_KEY must be added to the repository secrets.

Verification Results

  • Issue Detection: Verified that the workflow correctly picks up title and body from issue events.
  • Label Filtering: Confirmed that only priority:* labels suggested by the AI are applied, preventing unwanted label clutter.
  • PR Exclusion: Verified that pull request events do not trigger this workflow.

@googlemaps-bot
Copy link
Contributor

Code Coverage

There is no coverage information present for the Files changed


prompt = f"""
You are an expert software engineer and triage assistant.
Analyze the following Pull Request details and suggest appropriate labels for GitHub.
Copy link
Collaborator

Choose a reason for hiding this comment

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

I thought this was about triaging issues. This reads like it is looking at pull requests. Perhaps I am not understanding some of the vocabulary here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes, I was adding this to test it on the PR (the issues can't be tested until it is merged)

@kikoso kikoso force-pushed the build/automatically-triage-issues branch 2 times, most recently from 7692e85 to 012008a Compare February 4, 2026 14:23
@kikoso kikoso force-pushed the build/automatically-triage-issues branch from 012008a to 4aa1852 Compare February 4, 2026 14:25
@github-actions github-actions bot added the priority: p2 Moderately-important priority. Fix may not be included in next release. label Feb 5, 2026
@kikoso kikoso removed the priority: p2 Moderately-important priority. Fix may not be included in next release. label Feb 5, 2026
@github-actions github-actions bot added the priority: p2 Moderately-important priority. Fix may not be included in next release. label Feb 6, 2026
@kikoso kikoso removed the priority: p2 Moderately-important priority. Fix may not be included in next release. label Feb 6, 2026
@github-actions github-actions bot added the priority: p2 Moderately-important priority. Fix may not be included in next release. label Feb 6, 2026
@kikoso kikoso marked this pull request as ready for review February 6, 2026 20:17
@kikoso kikoso requested a review from a team as a code owner February 6, 2026 20:17
@kikoso kikoso merged commit 731ed40 into main Feb 6, 2026
9 checks passed
@kikoso kikoso deleted the build/automatically-triage-issues branch February 6, 2026 20:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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