Restore automatic spam issue closure - #14088
Merged
Merged
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: e00d0ec3-c3d6-4ee7-9100-a7f294fe2402
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: e00d0ec3-c3d6-4ee7-9100-a7f294fe2402
Contributor
There was a problem hiding this comment.
Pull request overview
This pull request updates the agentic issue-triage workflow to restore automatic spam issue closure by regenerating the compiled workflow with gh-aw v0.85.4 (so labels carrying issue-intent metadata are applied via GraphQL), and preserves the prior noop reporting behavior that changed across runtime versions.
Changes:
- Preserve legacy behavior by explicitly setting
noop.report-as-issue: truein the workflow frontmatter. - Regenerate
.github/workflows/issue-triage.lock.ymlto pingh-aw v0.85.4and pick up the newer compiled job wiring (including updated images/scripts and new failure-reporting behavior).
Show a summary per file
| File | Description |
|---|---|
| .github/workflows/issue-triage.md | Adds explicit noop.report-as-issue: true to preserve prior reporting behavior after the gh-aw upgrade. |
| .github/workflows/issue-triage.lock.yml | Regenerated lockfile compiled by gh-aw v0.85.4, updating pinned action SHAs/images and compiled workflow logic. |
Review details
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 2/2 changed files
- Comments generated: 1
- Review effort level: Lite
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com> Copilot-Session: e00d0ec3-c3d6-4ee7-9100-a7f294fe2402
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.
Description
The issue-triage agent correctly emits
suspected-spamwithoutsuggest, but gh-aw v0.83.4 sends metadata-bearing labels through the REST label endpoint. GitHub accepts that request without applying the label, so the existing label-triggered spam closer never runs.This is tracked upstream in github/gh-aw#50631, where the safe-output artifact shows
labelsAddedpopulated while the before and after label sets remain empty. github/gh-aw#50637 fixes the regression, and the v0.85.4 release notes explicitly list “Fixedadd_labelssilently applying no labels.”Regenerate the workflow with gh-aw v0.85.4, which routes labels containing issue-intent metadata through GraphQL. This restores direct
suspected-spamapplication and therefore the existing comment,needs-triageremoval, and issue closure behavior.How did you test this change?
gh aw compile --dir .github/workflows --validate: 1 workflow succeeded with 0 warnings in an isolated repository; the generated lockfile matches the committed lockfile.2709137ea6c5b0e19aa621454dc643ea8dc526b1).Report failed jobsstep is absent after explicitly preserving the v0.83.4 reporting behavior.go test ./...fails identically at base commit5c39f803fand on this branch in existing git/auth configuration tests.make lintfails identically at base commit5c39f803fand on this branch with three existinggovetreflect.Ptrdiagnostics.Key points
noop.report-as-issue: true, whose implicit default changed in gh-aw v0.85.4.Notes for reviewers
Start with
.github/workflows/issue-triage.md, then confirm the generated.github/workflows/issue-triage.lock.ymlpins gh-aw v0.85.4. This is a follow-up to #14027.Authorship and follow-up
Who wrote this:
Who answers review comments: