Fix stale lock file for issue-triage workflow - #8428
tay1orjones with Copilot wants to merge 2 commits into
Conversation
|
Co-authored-by: tay1orjones <3360588+tay1orjones@users.noreply.github.com>
There was a problem hiding this comment.
🟢 Approval recommended
The compiled lock file is synchronized with its source, with no unresolved review issues.
Pull request overview
Regenerates the issue-triage workflow lock file to match its source and clear stale-lock validation.
Changes:
- Refreshes the embedded frontmatter hash.
- Adds
id-token: noneto the activation job permissions.
File summaries
| File | Description |
|---|---|
.github/workflows/issue-triage.lock.yml |
Regenerated workflow artifact metadata and permissions. |
Review details
- Files reviewed: 1/1 changed files
- Comments generated: 0
- Review effort level: Lite
💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.
|
Issue triage's agentic workflow was failing to run because
issue-triage.lock.ymlno longer matched itsissue-triage.mdsource, tripping gh-aw's stale-lock-file guard.Changes
.github/workflows/issue-triage.lock.ymlfrom.github/workflows/issue-triage.mdusinggh-aw compile(v0.88.2)id-token: nonepermission to the activation job and refreshes the embedded frontmatter hash so the lock file matches source againNo changes to workflow behavior or source markdown; this is a regeneration of the compiled artifact only.
Changelog
New
Changed
issue-triage.lock.ymlto sync withissue-triage.mdRemoved
Rollout strategy
Generated GitHub Actions workflow file, not part of the published
@primer/reactpackage.Testing & Reviewing
Verified
gh-aw compile issue-triageproduces no further diff, confirming the lock file is now in sync with its source markdown.