Repository navigation
Recover public GitHub readers and simplify failure pages - #23
Merged
Merged
Conversation
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
1 participant
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.
The public repository reader stopped at GitHub’s redirects for renamed or moved repositories, returning a 503. It now follows at most two redirects to HTTPS GitHub API issue/comment endpoints, preserving pagination/filter query bounds and one shared four-second timeout. It never forwards incoming authorization or cookies and never writes external reader content into canonical D1 publishing.
Error pages offer a distinct GitHub fallback and retain native navigation/footer while omitting promotional extensions. Successful readers retain their shared footer. Product checks exclude linked agent-tooling folders while preserving application tests.
Validation: complete
pnpm checkand startup check pass (77 tests, typecheck, lint, formatting, client budgets and Worker dry-run). Parent independently reran the public Worker suite. Regressions cover moved repositories, missing/replaced queries, unsafe destinations, two-hop issue/comments, shared timeout, credential isolation, canonical reads and successful/error footer behavior.