feat(uk-ai-resilience): create up to 2 labeled issues for top-priority findings#42636
Merged
Merged
Conversation
Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add functionality to create high-priority issues
feat(uk-ai-resilience): create up to 2 labeled issues for top-priority findings
Jul 1, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
This PR extends the UK AI Operational Resilience gh-aw workflow to optionally turn the highest-priority Tier B/C/D findings into up to two labeled GitHub issues per run, while keeping the existing discussion report behavior intact and regenerating the compiled workflow output.
Changes:
- Added the
issuesGitHub toolset so the agent can query existing open issues for deduplication. - Added a
safe-outputs.create-issueconfiguration capped atmax: 2with predefined labels and a title prefix. - Updated the workflow prompt with a new “Phase 6” instructing the agent to select and file up to two top-priority findings as issues.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/uk-ai-operational-resilience.md |
Adds issues toolset, configures safe-outputs.create-issue, and introduces Phase 6 prompt requirements for issue creation/deduplication. |
.github/workflows/uk-ai-operational-resilience.lock.yml |
Regenerates compiled workflow to include the new safe-output tool (create_issue) and updated handler configuration. |
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: Low
Comment on lines
+209
to
+217
| Create at most **2** GitHub issues per run for the highest-priority Tier B/C/D findings: | ||
|
|
||
| - Prioritize Tier C/D findings first, then highest `remediation_priority` (`critical`, then `high`). | ||
| - Before creating an issue, check for duplicate open issues and skip duplicates. | ||
| - Each issue body must include: | ||
| - tier and risk-scoring breakdown | ||
| - remediation action and SLA urgency | ||
| - discussion report link | ||
| - Do not exceed 2 issues in total for the run. |
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.
This updates the UK AI Operational Resilience workflow to turn the highest-priority Tier B/C/D findings into actionable GitHub issues, capped at two per run. The discussion report output remains unchanged; issue creation is additive and constrained.
Workflow behavior updates
safe-outputs.create-issuewith:max: 2labels: [security, high-priority, ai-generated]title-prefix: "[uk-ai-resilience] "issuesto the GitHub toolsets so the agent can check open issues before creating new ones.Prompt logic for issue creation
critical/highremediation priority),Compiled workflow output
.lock.ymlto reflect the new safe-output/tooling and prompt behavior.