Skip to content

fix(rulesets): tolerate 403 on the rulesets fetch#51

Merged
lex00 merged 1 commit into
mainfrom
fix/rulesets-tolerate-403
Jun 19, 2026
Merged

fix(rulesets): tolerate 403 on the rulesets fetch#51
lex00 merged 1 commit into
mainfrom
fix/rulesets-tolerate-403

Conversation

@lex00

@lex00 lex00 commented Jun 19, 2026

Copy link
Copy Markdown
Contributor

Surfaced by the live e2e: GET /orgs/{org}/rulesets 403s when the App lacks that scope (and organization_administration: read doesn't cover it), but fetchRulesets only caught 404 — so an inaccessible org-rulesets read aborted the whole rulesets cycle, including repo rulesets.

Fix: treat 403 like 404 (return empty), matching how the token cycles degrade gracefully. So org-rulesets-inaccessible never blocks repo-rulesets reconciliation.

+1 unit test; action bundle rebuilt; 21 rulesets tests green.

🤖 Generated with Claude Code

The live e2e surfaced it: GET /orgs/{org}/rulesets 403s when the App
lacks that scope, and fetchRulesets only caught 404 — so an inaccessible
org-rulesets read aborted the whole cycle (incl. repo rulesets). Treat
403 like 404 (return empty), matching the token cycles' graceful
degradation. +1 unit test; action bundle rebuilt.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@lex00 lex00 merged commit 031ee0e into main Jun 19, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant