Skip to content

fix: correct firewall issue dispatcher tracking issue link format #2161

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lpcox merged 2 commits into from
Apr 23, 2026
Merged

fix: correct firewall issue dispatcher tracking issue link format #2161

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d313f6d
fix: clarify numeric issue URL formatting in dispatcher workflow source
Copilot Apr 23, 2026
d882803
fix: recompile firewall issue dispatcher lock workflow
Copilot Apr 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 20 additions & 20 deletions .github/workflows/firewall-issue-dispatcher.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

7 changes: 5 additions & 2 deletions .github/workflows/firewall-issue-dispatcher.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -82,9 +82,12 @@ For each **unprocessed** issue:
2. **Comment on the original `github/gh-aw` issue** linking to the newly created tracking issue. Use this exact format:
> 🔗 AWF tracking issue: https://github.com/github/gh-aw-firewall/issues/{NUMBER}

where `{NUMBER}` is replaced with **only the numeric issue number** (e.g., `1896`). Do NOT include the repository name, hash symbols, or any other text — just the number in the URL path. Use the `add_comment` safe output tool with `repo: "github/gh-aw"` and the original issue number.
`create_issue` may return a reference like `github/gh-aw-firewall#2159`. Extract only the trailing digits before composing the URL.
- Valid: `https://github.com/github/gh-aw-firewall/issues/2159`
- Invalid: `https://github.com/github/gh-aw-firewall/issues/github/gh-aw-firewall#2159`
- Invalid: `https://github.com/github/gh-aw-firewall/issues/#2159`

where `{NUMBER}` is replaced with **only the numeric issue number** (e.g., `1896`). Do NOT include the repository name, hash symbols, or any other text — just the number in the URL path. Use the `add_comment` safe output tool with `repo: "github/gh-aw"` and the original issue number.
Use the `add_comment` safe output tool with `repo: "github/gh-aw"` and the original issue number.
Comment on lines +85 to +90
Copy link

Copilot AI Apr 23, 2026

Choose a reason for hiding this comment

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

This workflow has a compiled companion .lock.yml and the compiled job includes a lock staleness check; updating the .md without regenerating firewall-issue-dispatcher.lock.yml will cause the workflow to report a stale lock file (and may keep the runtime prompt out of sync). Please run gh aw compile and commit the updated .github/workflows/firewall-issue-dispatcher.lock.yml in this PR.

Copilot uses AI. Check for mistakes.

### 4. Report Results

Expand Down
Loading