feat: add SHA-bound remote repository context acquisition - #300
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Wibias
marked this pull request as ready for review
August 19, 2026 20:46
Wibias
enabled auto-merge
August 19, 2026 20:47
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.
What changed
scripts/repository-context.mjsto resolveowner/repoor GitHub URLs, discover the real default branch, optionally pin a workflow-selected branch, capture its exact commit SHA, and read files against that immutable SHAreferences/repository-context.mdwith the remote-first acquisition ladder and explicit escalation rules for history, runtime, exhaustive analysis, and modificationGD-EVID-007so workflows that already load the evidence policy can compose this capability without adding a new public routeWhy
GitHub Delivery sometimes needs repository context before a useful local checkout exists. The existing options either assume a checkout or encourage moving-branch/raw reads. This adds a bounded read-only path that keeps substantive evidence tied to an immutable snapshot and avoids guessing
main,master, orHEAD.The capability is intentionally internal. It does not add a new lifecycle route, mutation authority, or a required gitmcp dependency.
Validation
node --test tests/unit/repository-context.test.mjs-> 8/8 pass in the isolated local mirror used for implementationnode --check scripts/repository-context.mjs-> passnode --check tests/unit/repository-context.test.mjs-> passFull repository
npm test/npm run checkwere not run locally because this execution environment cannot resolve GitHub to clone the repository. CI on this PR remains the authoritative full-repository validation.