-
Notifications
You must be signed in to change notification settings - Fork 17
fix: restore create-issue step and improve URL format in firewall-issue-dispatcher #1910
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.
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
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change | ||
|---|---|---|---|---|
|
|
@@ -65,20 +65,27 @@ gh api graphql -f query=' | |||
|
|
||||
| ## Step 2: Filter Locally | ||||
|
|
||||
| For each issue found, read its comments and check whether any comment contains a reference to a `github/gh-aw-firewall` issue (i.e., a URL matching `https://github.com/github/gh-aw-firewall/issues/` or a GitHub cross-repo reference matching `github/gh-aw-firewall#`). If such a comment exists, **skip** that issue — it has already been audited. | ||||
| For each issue found, read its comments and check whether any comment contains a reference to a `github/gh-aw-firewall` issue (i.e., a URL matching `https://github.com/github/gh-aw-firewall/issues/` or a GitHub cross-repo reference matching `github/gh-aw-firewall#`). If such a comment exists, **skip** that issue — it has already been audited. Do this filtering in your analysis — do NOT make additional API calls. | ||||
|
|
||||
| If no unprocessed issues remain, call `noop` and stop. | ||||
|
|
||||
| ## Step 3: Create Tracking Issues | ||||
|
|
||||
| For each **unprocessed** issue: | ||||
|
|
||||
| 4. **Comment on the original `github/gh-aw` issue** linking to the newly created tracking issue. Use this exact format: | ||||
| 1. **Create a tracking issue in `github/gh-aw-firewall`** using the `create_issue` safe output with: | ||||
| - Title: `[awf] <component>: <summary>` | ||||
| - Body: **Problem**, **Context** (link to original), **Root Cause**, **Proposed Solution** | ||||
| - Labels: `awf-triage` | ||||
| - Reference specific source files. See `AGENTS.md` for component descriptions. | ||||
|
|
||||
| 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. | ||||
|
|
||||
| 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. | ||||
|
|
||||
|
Comment on lines
+87
to
+88
|
||||
| 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. |
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR description mentions reverting the cron minute in
firewall-issue-dispatcher.lock.ymlback to11 */6 * * *, but the lock file currently still hascron: "20 */6 * * *"(see.github/workflows/firewall-issue-dispatcher.lock.yml:42). Please update the lock workflow schedule if the20minute value was unintended.