Repository navigation
chore: drop the 403 blob-restriction case in downloadBlob - #58
Merged
Merged
Conversation
The API removed branch-based blob restrictions (OSWatcher/graphql-api#70), so a download can no longer return 403 for a restricted blob. Fold that branch into the generic failure path. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014WnrRvhmHcMPj6iwJ2NnzK
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.
graphql-api#70 removes branch-based blob restrictions, so
GET /blob/:hashcan no longer return 403 for a "restricted" blob.downloadBlob()insrc/utils/filesystem.tshad a special case for that status; fold it into the generic failure path.Validation
npm run lint,npm run type-check,prettier --checkpass🤖 Generated with Claude Code