Repository navigation
Conversation
|
Warning Review limit reachedYou've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Next included review available in 33 minutes. View limit details
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 |
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Changelog✅ Contribution check passed. Head: Base: Contribution: 1 new valid fragment(s). Policy: ordinary.
|
Code Coverage Report: Only Changed Files listed
Minimum allowed coverage is |
|
@codex review |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ac05e402a8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
🛡️ Codex Security Review · Automatically triggeredSecurity review completed. No security issues were found in this pull request. Reviewed commit: Only the user who started this review can view the report in Codex. ℹ️ About Codex security reviews in GitHubThis is an experimental Codex feature. Security reviews are triggered when:
Once complete, Codex will leave suggestions, or a comment if no findings are found. |
|
Incorporated by #78, merged as |
Version preparation can refuse a valid squash-merged contribution when its original PR head is absent from a full main-only checkout. After verifying repository, merged PR/head, ancestry and complete file/commit evidence, the resolver acquires only that exact SHA and rechecks local commit identity and repository/PR API authority before proving direct implementation provenance.
Acquisition uses authenticated HTTPS discovery and a minimal exact-head Git upload-pack request to github.com. The supplied token stays inside the HTTP adapter, including for private repositories; redirects are disabled. A complete response is bounded to 64 MiB and imported by local git index-pack --stdin --strict. Credentials never reach Git processes, argv, environment, config, helpers or persisted files. Native Git authentication would violate the existing HTTP-only credential boundary.
Refs, FETCH_HEAD, index and managed files remain unchanged during acquisition, including previews. Failed authentication, malformed packs or changed evidence refuse preparation. Existing local Enterprise heads remain supported; missing Enterprise heads fail closed because their Git transport host is not verified. Ownership, signatures and managed-PR validation remain unchanged.
Validation at 81e3a8f: full unit suite 2,849 tests / 17,991 assertions; 100% executable source coverage (6,253/6,253 lines, every class); two disposable private-transport integration cases / 135 assertions using real git upload-pack and index-pack for authenticated success and HTTP 401 refusal; PHP syntax, 587 PHPDoc contracts, 45 quality-helper fixtures, Rector, ECS and fragment validation passed. Composer plugins stayed disabled for quality execution.
Includes one patch fragment and documents authentication, the response limit and Enterprise boundary. No live consumer recovery, merge or publication is claimed.