fix: improve PR fetch error handling and document fine-grained PAT 403 issue#90
Merged
unhappychoice merged 1 commit intomainfrom Apr 5, 2026
Merged
Conversation
…3 issue - Retry only on 429 (rate limit), not on 403 (permission/policy errors) - Log response body message on 403 so users can see the actual cause - Add inter-request delay (200ms) to respect GitHub API best practices - Document the fine-grained PAT organization lifetime policy issue in troubleshooting.md with references and workarounds
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
docs/troubleshooting.mdBackground
When using a fine-grained PAT with a lifetime exceeding 366 days, GitHub's default organization token policy blocks API access to repositories in organizations the user belongs to, even for public repositories. This causes
403 Forbiddenerrors during PR fetching.The error message from GitHub is:
This is an inconsistency in GitHub's implementation: the approval policy correctly exempts public resources, but the lifetime policy does not. The same issue has been reported in composer/composer#12711.
Previously, the error was logged as just
403 Forbiddenwithout the response body, making it impossible for users to diagnose the cause.