ci: handle SARIF polling disabled errors#69
Conversation
PR SummaryLow Risk Overview When GitHub returns a 403 indicating Code Scanning/Advanced Security is disabled, the script now exits cleanly with a GitHub Actions warning instead of failing during polling; all other HTTP errors still surface the response body on stderr and are re-raised. Adds focused tests covering the skip-on-disabled behavior and the re-raise path for non-disabled HTTP errors. Reviewed by Cursor Bugbot for commit a84dfb0. Bugbot is set up for automated code reviews on this repo. Configure here. |
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix prepared a fix for the issue found in the latest run.
- ✅ Fixed: Misleading return type creates latent UnboundLocalError risk
- Updated the helper to return
Literal[True]and removed the fragile false-branch handling at both call sites so unbound variables cannot be reached.
- Updated the helper to return
You can send follow-ups to the cloud agent here.
Reviewed by Cursor Bugbot for commit a84dfb0. Configure here.

Summary
Test
Note: local pre-commit was skipped because the installed macOS bash 3.2 lacks mapfile used by the hook; this change has no staged Go files and Python checks above passed.
Fixes missed review feedback from #67.