ci: triage new issues with Codex - #1257
Open
DaleSeo wants to merge 1 commit into
Open
Conversation
DaleSeo
force-pushed
the
DaleSeo/issue-triage
branch
from
September 10, 2026 23:20
063bf63 to
bc2e160
Compare
DaleSeo
force-pushed
the
DaleSeo/issue-triage
branch
from
September 10, 2026 23:27
bc2e160 to
34957bb
Compare
DaleSeo
marked this pull request as ready for review
September 10, 2026 23:36
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation and Context
triage.ymlhas been disabled withif: falsesince #714. This PR replaces the disabled Bash triage script with a AI-powered workflow that labels new issues. As guided in Maintain Codex account auth in CI/CD, the workflow restoresauth.jsonfrom a secret, refreshes it during the run, and writes it back afterward.This repository has two configured secrets,
CODEX_AUTH_JSONandCODEX_AUTH_STORE_TOKEN. The second one is a fine-grained PAT becauseGITHUB_TOKENdoes not have thesecretsscope and cannot persist the refreshed file.How Has This Been Tested?
Tested via
workflow_dispatchagainst issue #1251:https://github.com/modelcontextprotocol/rust-sdk/actions/runs/34541690342
Breaking Changes
None.
Types of changes
Checklist