Skip to content

Reduce Refactoring Scanner AI-credit burn from duplicate-issue lookups #5125

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 3 commits into from
Jun 16, 2026
+4 −3
Merged

Reduce Refactoring Scanner AI-credit burn from duplicate-issue lookups #5125

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ab445dd
Initial plan
Copilot Jun 16, 2026
5285a13
fix: reduce refactoring scanner issue-query context
Copilot Jun 16, 2026
de05f4e
Potential fix for pull request finding
lpcox Jun 16, 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
2 changes: 1 addition & 1 deletion .github/workflows/refactoring-scanner.lock.yml
View file
Open in desktop

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

5 changes: 3 additions & 2 deletions .github/workflows/refactoring-scanner.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -184,8 +184,9 @@ Before creating new issues, check BOTH open AND closed issues:

1. Search for issues with `[Refactoring]` prefix mentioning the same file using `state: all` (or equivalent `is:open` + `is:closed`)
2. Search for issues with labels `code-quality` or `refactoring` mentioning the same file using `state: all` (or equivalent `is:open` + `is:closed`)
3. Skip any finding that already has an open tracking issue
4. For matching closed issues, check the GitHub `state_reason`: **auto-skip only when `state_reason` is `not_planned`** (often shown as "won't fix" / "not planned"). If `state_reason` is `completed` and the finding still reproduces, reopen the prior issue or file a new one with fresh evidence and a link to the prior issue.
3. Use metadata-only issue queries (number/title/state/stateReason/labels/url). **Do not fetch issue bodies** unless strictly required.
4. Skip any finding that already has an open tracking issue
5. For matching closed issues, check GitHub `stateReason` (`state_reason` in REST): **auto-skip only when the reason is "not planned" (`NOT_PLANNED` / `not_planned`)** (often shown as "won't fix" / "not planned"). If the reason is "completed" (`COMPLETED` / `completed`) and the finding still reproduces, reopen the prior issue or file a new one with fresh evidence and a link to the prior issue.

## Phase 6: Prioritize and File Issues

Expand Down
Loading