fix: compile issue-triage agentic workflow so it runs on new issues#211
Merged
Conversation
The issue-triage.md gh-aw source was never compiled into an issue-triage.lock.yml, so GitHub Actions never registered or ran it. Newly opened issues received no triage labels or recommendation comment. - Add frontmatter to issue-triage.md (permissions: copilot-requests: write, Node 22 runtime pin, timeout) matching doc-freshness, so the workflow uses GitHub Actions token-based inference instead of a COPILOT_GITHUB_TOKEN PAT (which the repo does not have configured). - Recompile all gh-aw workflows with the latest gh-aw (v0.81.6): - Add issue-triage.lock.yml (the executable workflow) - Recompile doc-freshness.lock.yml (toolchain version bumps only) - Add auto-generated agentics-maintenance.yml - Bump github/gh-aw-actions/setup pin to v0.81.6 in actions-lock.json Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Node 24 is the current Active LTS; Node 22 is now Maintenance LTS. The repo has no native dependencies and package.json engines already allows >=22, so moving the runtime up is low risk. Verified locally on Node 24.13.1: npm ci, lint, and all 1066 tests pass. - ci.yml: run the PR test job as a matrix over Node ['22', '24'] so the engines floor (22) stays covered while adding Active LTS (24). The gated, cost-protected integration-* and squad-release workflows are intentionally left on a single Node version (not matrixed) to avoid doubling approvals/cost. - issue-triage.md / doc-freshness.md: remove the runtimes.node "22" pin so the agent jobs run on gh-aw's default Node 24, matching CI. Both lock files recompiled accordingly. engines is intentionally left at >=22.0.0 (no change to consumer support). Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Contributor
Author
|
@copilot - update the integration workflows (not CI) to use node version 24 |
Contributor
Done. Updated |
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes GitHub Agentic Workflow registration for issue triage by adding the missing compiled workflow (.lock.yml) and updating gh-aw-generated artifacts/pins so the workflow can actually run on newly opened issues.
Changes:
- Adds missing executable workflow: compiles
.github/workflows/issue-triage.mdinto.github/workflows/issue-triage.lock.yml. - Recompiles existing gh-aw workflow lock output and introduces the generated
agentics-maintenance.yml. - Updates Node versions used in CI/integration workflows and bumps
.github/aw/actions-lock.jsonto gh-awv0.81.6.
Reviewed changes
Copilot reviewed 8 out of 9 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/issue-triage.md |
Adds frontmatter (permissions/timeout) for gh-aw issue triage source workflow. |
.github/workflows/issue-triage.lock.yml |
New compiled gh-aw workflow that GitHub Actions can execute on issues: opened. |
.github/workflows/doc-freshness.md |
Updates doc-freshness source (removes Node runtime pin block). |
.github/workflows/doc-freshness.lock.yml |
Recompiled output with updated gh-aw/tooling versions and runtime details. |
.github/workflows/agentics-maintenance.yml |
New generated maintenance workflow for gh-aw safe-outputs cleanup/ops. |
.github/aw/actions-lock.json |
Updates gh-aw action pins to v0.81.6 (adds setup-cli entry). |
.github/workflows/ci.yml |
Runs tests on a Node version matrix (22 and 24). |
.github/workflows/integration-test.yml |
Updates Node version used during integration roundtrip job to 24. |
.github/workflows/integration-redact-secrets.yml |
Updates Node version used during redaction integration job to 24. |
petehauge
previously approved these changes
Jul 2, 2026
Integrate latest main, which renamed the integration workflows and added new gh-aw issue workflows. Conflicts resolved: - integration-test.yml -> test-round-trip.yml (rename/modify): kept the rename and applied this branch's Node 24 change to the renamed file. - integration-redact-secrets.yml -> test-redact-secrets.yml (rename/modify): same — Node 24 applied to the renamed file. - ci.yml (modify/modify): kept both main's workflow_call trigger and this branch's Node [22, 24] test matrix. - .github/aw/actions-lock.json (modify/modify): regenerated by recompiling all gh-aw workflows with gh-aw v0.81.6, producing a single consistent pin set (setup@v0.81.6, setup-cli@v0.81.6, github-script@v8). Recompiled all four gh-aw workflows (doc-freshness, issue-triage, issue-assign, issue-clarify) so every workflow and the shared actions-lock.json target gh-aw v0.81.6. This also corrects a latent skew on main where issue-assign/issue-clarify were compiled with v0.81.6 but still pinned the setup action at v0.80.9. Verified on Node 24.13.1: npm run lint and all 1066 tests pass; gh aw compile reports 0 errors / 0 warnings. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
petehauge
approved these changes
Jul 2, 2026
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.
Summary
Newly opened issues (e.g. #210) were not being triaged — no advisory labels, no recommendation comment. Root cause:
issue-triage.mdwas never compiled into an executableissue-triage.lock.yml, so GitHub Actions never registered or ran the workflow.gh-aw (GitHub Agentic Workflows) sources are
.mdfiles that must be compiled into.lock.ymlfiles; GitHub Actions only runs the.lock.yml.doc-freshnesshad both files, butissue-triagehad only the.mdsource, so no "Issue Triage" workflow existed in the Actions registry at all.What this delivers
issue-triage.md:permissions.copilot-requests: write, Node 22 runtime pin, and a timeout — matching the workingdoc-freshnessworkflow. This makes it use GitHub Actions token-based inference (COPILOT_GITHUB_TOKEN: ${{ github.token }}) instead of requiring aCOPILOT_GITHUB_TOKENPAT secret, which this repo does not have configured. Without this, the as-generated workflow would have failed at a mandatory secret-validation step.issue-triage.lock.yml— the executable workflow (the actual fix)doc-freshness.lock.yml— toolchain version bumps only (firewall images0.27.7→0.27.11, Copilot CLI1.0.63→1.0.65, awf/mcpg bumps); no change to its triage/logicagentics-maintenance.yml— emitted by v0.81.6 for repos using expiring safe-outputs (scheduled cleanup; can be disabled via.github/workflows/aw.json{"maintenance": false})github/gh-aw-actions/setuppin tov0.81.6in.github/aw/actions-lock.jsonVerification
issue-triagewas absent from the Actions workflow registry, whiledoc-freshness.lock.ymlwas registered and active.issue-triage.lock.ymlno longer requires a PAT (usesgithub.token) and pins Node 22 — matchingdoc-freshness.type:documentation,type:question,effort:*,duplicate, etc.) exist in the repo.gh aw compile→ 2 workflow(s): 0 errors, 0 warnings. Lock files stored as LF per.gitattributes.Files
.github/workflows/issue-triage.md(modified — frontmatter).github/workflows/issue-triage.lock.yml(new).github/workflows/doc-freshness.lock.yml(recompiled).github/workflows/agentics-maintenance.yml(new, generated).github/aw/actions-lock.json(setup action pin bump)Notes
doc-freshness).main, the workflow triggers onissues: [opened]. It won't retroactively triage Latest changes #210, which was opened before the fix..squad/identity/constitution.mdis the standard ceremony; these are.github/workflow files (nosrc//tests/changes).