Conversation
Adds an agentic workflow that runs every 6 hours to audit github/gh-aw issues labeled 'awf' and creates tracking issues in gh-aw-firewall with problem analysis and proposed solutions. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
✅ Coverage Check PassedOverall Coverage
📁 Per-file Coverage Changes (1 files)
Coverage comparison generated by |
There was a problem hiding this comment.
Pull request overview
Adds a new gh-aw agentic workflow that periodically triages github/gh-aw issues labeled awf by creating corresponding tracking issues in github/gh-aw-firewall, then back-linking via a comment.
Changes:
- Introduces the
awf-issue-auditoragent prompt/workflow definition (.md). - Adds the compiled/locked GitHub Actions workflow (
.lock.yml) for scheduled + manual runs. - Updates the repo’s action pin lockfile to include
github/gh-aw-actions/setup@v0.63.0.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| .github/workflows/awf-issue-auditor.md | Defines the agent instructions, repo allowlist, and safe-output constraints for cross-repo auditing. |
| .github/workflows/awf-issue-auditor.lock.yml | Generated compiled workflow implementing the scheduled agent run, MCP gateway, and safe output processing. |
| .github/aw/actions-lock.json | Adds the pinned github/gh-aw-actions/setup@v0.63.0 entry required by the new compiled workflow. |
Comments suppressed due to low confidence (2)
.github/workflows/awf-issue-auditor.md:45
- The skip heuristic only checks for a full URL to
github/gh-aw-firewall/issues/.... In this repo, tracking links are sometimes written as plain text (e.g.gh-aw-firewall issue #123), so this could create duplicate tracking issues for already-audited items. Consider matching both URL links and the commongh-aw-firewall issue #<n>pattern (and/or checking issue body as well as comments).
### 2. Filter Out Already-Audited Issues
For each issue found, read its comments and check whether any comment contains a link to a `github/gh-aw-firewall` issue (i.e., a URL matching `https://github.com/github/gh-aw-firewall/issues/`). If such a comment exists, **skip** that issue — it has already been audited.
.github/workflows/awf-issue-auditor.md:41
- Safe outputs are capped at 10
create-issue+ 10add-commentactions per run, but the prompt currently instructs the agent to search/process all matching issues. To avoid wasted runtime and partial/non-deterministic processing when limits are hit, consider explicitly telling the agent to process at most 10 unprocessed issues per run (and define an ordering, e.g. oldest-first).
### 1. List AWF-Labeled Issues
Search for all **open** issues in `github/gh-aw` with the label `awf`.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| ### 1. List AWF-Labeled Issues | ||
|
|
||
| Search for all **open** issues in `github/gh-aw` with the label `awf`. |
There was a problem hiding this comment.
Step 1 says to "Search for all open issues" with label awf, but GitHub search commonly includes pull requests unless is:issue is specified. To avoid accidentally creating firewall tracking issues for PRs, update the instructions to explicitly include is:issue in the query (e.g. repo:github/gh-aw is:open is:issue label:awf).
This issue also appears in the following locations of the same file:
- line 38
- line 42
| Search for all **open** issues in `github/gh-aw` with the label `awf`. | |
| Search for all **open** issues in `github/gh-aw` with the label `awf` using this query: `repo:github/gh-aw is:open is:issue label:awf`. |
| github-token: ${{ secrets.GH_AW_CROSS_REPO_PAT }} | ||
| create-issue: | ||
| max: 10 | ||
| labels: [awf-triage] |
There was a problem hiding this comment.
create-issue isn’t constrained to only create issues in github/gh-aw-firewall (there’s no repo allowlist/target specified for it), while the safeoutputs write-sink accepts both github/gh-aw and github/gh-aw-firewall. If the intent is to only create tracking issues in gh-aw-firewall, consider adding a repo restriction/target for create-issue (if supported by safe-outputs config) so the agent can’t create issues in github/gh-aw by mistake.
| labels: [awf-triage] | |
| labels: [awf-triage] | |
| allowed-repos: ["github/gh-aw-firewall"] |
|
Smoke Test Results — PASS
|
|
Smoke test results for run 23615672892:
Overall: PASS PR author:
|
🏗️ Build Test Suite Results
Overall: 8/8 ecosystems passed — ✅ PASS
|
|
🔮 Oracle smoke ledger for PR #1459
Warning
|
Summary
Adds an agentic workflow (
awf-issue-auditor) that runs every 6 hours to audit issues ingithub/gh-awlabeledawfand creates corresponding tracking issues ingh-aw-firewall.What it does
github/gh-awwith theawflabelgh-aw-firewallissuegh-aw-firewallwith:gh-awissue with a link to the new tracking issueConfiguration
GH_AW_CROSS_REPO_PATsecret for readinggh-awand writing to both reposnone(reads all issue content regardless of author association)awf-triagePrerequisites
GH_AW_CROSS_REPO_PATrepository secret with access to bothgithub/gh-aw(read) andgithub/gh-aw-firewall(write)