Skip to content

ci: combine AI issue triage with a maintainer rotation as the responsible reviewer - #1260

Open
alexhancock wants to merge 2 commits into
mainfrom
alexhancock/ai-triage-with-human-backstop
Open

ci: combine AI issue triage with a maintainer rotation as the responsible reviewer#1260
alexhancock wants to merge 2 commits into
mainfrom
alexhancock/ai-triage-with-human-backstop

Conversation

@alexhancock

@alexhancock alexhancock commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Motivation and Context

Supersedes #1257 and #1254 by combining the ideas. This combines both into a single triage.yml with two stages:

  1. Codex classifies the issue and applies type / priority / component labels.
  2. The maintainer on rotation is assigned as the responsible human reviewer, @-mentioned with what the AI concluded so they're confirming a verdict rather than starting cold.

Codex classification is scoped to issues only. PRs already get their T-* labels from the diff via auto-label-pr.yml, so running the model over them wouldn't serve much triaging purpose.

Also addresses @DaleSeo's feedback on #1254

How Has This Been Tested?

  • actionlint clean
  • Both stages support workflow_dispatch with dry_run (default true) which logs the verdict and the rotation pick and changes nothing
  • This can be fully tested when the secrets are configured on the repo.

Breaking Changes

N/A

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation update

Checklist

  • I have read the MCP Documentation
  • My code follows the repository's style guidelines
  • New and existing tests pass locally
  • I have added appropriate error handling
  • I have added or updated documentation as needed

@github-actions github-actions Bot added T-documentation Documentation improvements T-CI Changes to CI/CD workflows and configuration T-config Configuration file changes labels Sep 11, 2026
@alexhancock
alexhancock force-pushed the alexhancock/ai-triage-with-human-backstop branch from 358347f to fa29cdf Compare September 12, 2026 01:29
Comment thread .github/workflows/triage.yml Outdated
Comment thread .github/workflows/triage.yml Outdated
Comment thread .github/workflows/triage.yml
alexhancock added a commit that referenced this pull request Sep 14, 2026
Addresses review feedback on #1260:

* actions/checkout was pinned to v5.0.0 in the classify job while every
  other workflow in the repo uses v7.0.1. Restored to v7.0.1.
* actions/github-script was pinned to 373c709c, which is the v9 annotated
  tag object rather than a commit, so the ref did not resolve. Replaced
  with 3a2844b7, the commit v9.0.0 dereferences to.
* The workflow re-triages on `reopened`. Assignment now no-ops when the
  item already has an assignee, so an existing owner is not swapped for
  whoever is on rotation the week it reopens, and no duplicate comment is
  posted. The check runs before the roster lookup.

- name: Install Codex
run: npm install -g @openai/codex

@alexhancock
alexhancock force-pushed the alexhancock/ai-triage-with-human-backstop branch from a4e54ea to 1aa6bd6 Compare September 14, 2026 19:33
@alexhancock
alexhancock force-pushed the alexhancock/ai-triage-with-human-backstop branch from 1aa6bd6 to 8d9deb3 Compare September 14, 2026 19:34
@alexhancock
alexhancock marked this pull request as ready for review September 14, 2026 19:35
@alexhancock
alexhancock requested a review from a team as a code owner September 14, 2026 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

T-CI Changes to CI/CD workflows and configuration T-config Configuration file changes T-documentation Documentation improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants