Skip to content

Fix issue triage workflow dispatches - #68997

Merged
DeagleGross merged 2 commits into
dotnet:mainfrom
DeagleGross:deaglegross-fix-issue-triage-workflow
Sep 2, 2026
Merged

Fix issue triage workflow dispatches#68997
DeagleGross merged 2 commits into
dotnet:mainfrom
DeagleGross:deaglegross-fix-issue-triage-workflow

Conversation

@DeagleGross

Copy link
Copy Markdown
Member

Summary

  • explicitly target the dispatched issue in label and issue-type safe outputs
  • require an existing area-* label before treating triage as a no-op
  • isolate generated jobs by issue so concurrent manual dispatches do not compete
  • regenerate the lock file with gh-aw v0.87.10

Validation

  • gh aw compile issue-triage-agent --strict

Explicitly target dispatch issues in safe outputs, require a real area label before no-oping, and isolate generated jobs by issue. Recompile with gh-aw v0.87.10.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d12ab2db-364a-453c-b77b-42690f2321b6
@DeagleGross
DeagleGross requested review from a team and wtgodbe as code owners September 2, 2026 14:35
Copilot AI lite review requested due to automatic review settings September 2, 2026 14:35

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot review overview

🟡 Changes recommended

Workflow-level concurrency in the generated .lock.yml still doesn’t key off workflow_dispatch’s issue_number, allowing parallel runs against the same issue to race when applying labels/comments.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Review tier: Lite
Findings: 1 Medium severity

New issues introduced by this change (1)
Severity Finding
Medium severity .github/​workflows/​issue-triage-agent.lock.yml — The workflow-level concurrency group doesn’t include github.event.inputs.issue_number, so two…
What changed in this PR

This PR updates the issue-triage-agent Agentic Workflows definition and its generated workflow to better support workflow_dispatch triage runs by targeting the dispatched issue explicitly and reducing cross-run contention.

Changes:

  • Adds a per-issue discriminator in the gh-aw workflow definition and clarifies safe-output usage to explicitly target the intended issue number.
  • Tightens the “no-op” condition to require an existing area-* label (not just subtype labels like docs/question).
  • Regenerates the compiled .lock.yml workflow and updates pinned gh-aw action versions via the actions lockfile.
File Description
.github/​workflows/​issue-triage-agent.md Adds per-issue job discrimination and updates prompt instructions to explicitly target the dispatched issue and refine no-op criteria.
.github/​workflows/​issue-triage-agent.lock.yml Regenerated compiled workflow using gh-aw v0.87.10, including updated runtime/setup plumbing and conclusion concurrency isolation.
.github/​aw/​actions-lock.json Updates pinned github/gh-aw-actions/setup entry to v0.87.10.

💡 Add a code-review agent skill for context-aware, tailored reviews. Learn more in the docs.

Comment thread .github/workflows/issue-triage-agent.lock.yml Outdated
@DeagleGross DeagleGross self-assigned this Sep 2, 2026
@DeagleGross DeagleGross added the area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework label Sep 2, 2026
@DeagleGross
DeagleGross enabled auto-merge (squash) September 2, 2026 14:45
Use the dispatched issue number in the workflow-level concurrency group and preserve queued runs for the same issue.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

Copilot-Session: d12ab2db-364a-453c-b77b-42690f2321b6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-infrastructure Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants