Skip to content

Updated triage flows#4274

Open
RickWinter wants to merge 2 commits into
Azure:mainfrom
RickWinter:aw_triage
Open

Updated triage flows#4274
RickWinter wants to merge 2 commits into
Azure:mainfrom
RickWinter:aw_triage

Conversation

@RickWinter
Copy link
Copy Markdown
Member

No description provided.

Copilot AI review requested due to automatic review settings April 24, 2026 19:15
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates the repository’s agentic issue triage workflow to a more explicit, rule-based decision flow, including customer vs. team classification and CODEOWNERS-based routing, and regenerates the compiled lock workflow and action pin metadata accordingly.

Changes:

  • Rewrites .github/workflows/issue-triage.md with a step-by-step triage decision flow (spam/labels gating, customer evaluation, label prediction, CODEOWNERS routing, standardized comments) and expanded prompt-injection defenses.
  • Regenerates .github/workflows/issue-triage.lock.yml with newer gh-aw tooling and updated pinned action/container versions.
  • Updates .github/aw/actions-lock.json to include the newly referenced action versions.

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 2 comments.

File Description
.github/workflows/issue-triage.md Replaces the previous guidance with a strict triage decision flow (customer evaluation, label prediction, CODEOWNERS routing, comment templates).
.github/workflows/issue-triage.lock.yml Regenerated compiled workflow reflecting new prompt + updated gh-aw runtime/actions/tooling.
.github/aw/actions-lock.json Adds pins for new/updated GitHub Actions versions used by the regenerated lock workflow.

Comment thread .github/workflows/issue-triage.md Outdated
Comment thread .github/workflows/issue-triage.md Outdated
Copy link
Copy Markdown
Member

@heaths heaths left a comment

Choose a reason for hiding this comment

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

Some suggestions, but I see nothing blocking.

Comment thread .github/workflows/issue-triage.md Outdated
Comment thread .github/workflows/issue-triage.md
Comment thread .github/workflows/issue-triage.md
Comment thread .github/workflows/issue-triage.md
Comment thread .github/workflows/issue-triage.md Outdated
Comment thread .github/workflows/issue-triage.md Outdated
reaction: eyes
roles: all
issues:
types: [opened]
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

This is 2 "tabs" over instead of 1. I see this elsewhere below. I worry this might not work as planned since initial "tabs" are less than this. I honestly don't know about their YAML parser. What editor did you use? If VSCode, make sure you install the suggested EditorConfig extension since that's what we primarily use for formatting a lot of file types.

Comment on lines -37 to +28
report-as-issue: false
report-failure-as-issue: true
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Did it really change names or did we have the wrong one before?

@heaths heaths added the EngSys This issue is impacting the engineering system. label May 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

EngSys This issue is impacting the engineering system.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants