Codex: fix redirect path format in CloudFront KVS#2849
Merged
Conversation
- Include current repo in codexRepositories when building resolver - Handle relative URIs in CollectRedirects path extraction - Add unit tests for same-repo, cross-repo, and path extraction Made-with: Cursor
Mpdreamz
approved these changes
Mar 4, 2026
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
2 participants
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.
What
/r/{repo}/{path}format in the CloudFront KeyValueStore instead of/elastic/{repo}/tree/main/{path}Why
/r/ai-guild/best-practices/tools), but redirects were being stored with the preview URL formatbest-practices/tools->toolsto fail because the stored keys did not match incoming requestsNotes
codexRepositorieswhen building the URI resolver so same-repo redirects use the codex path formatMade with Cursor