Repository navigation
Add an immutable reusable repository baseline - #24
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
@codex review Please review this complete PR at head |
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. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 04b282e50e
ℹ️ 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. |
Add a reusable hygiene baseline for newly initialized repositories. The base-owned caller admits same-repository
pull_request_targetand main pushes, verifies the exact candidate head, and checks workflows, whitespace and secrets with immutable tools. Candidate programs are never executed; workflow lint does not load local action metadata.Review corrections reject redirected/nonregular workflow paths before stdin linting and retrieve the candidate through the base repository's PR ref. Fork PRs are explicitly unsupported in v1; checkout's default fork protection remains enabled. Existing required workflows and permissions remain intact.
Validation on
83967987ca23cc8b8eda60975eda320e434fb7bd: 40 unit tests passed, with one existing Linux-only test skipped on macOS; nine real-actionlint regression cases, actual Gitleaks historical-secret regressions, workflow/shell/JavaScript syntax and whitespace checks passed. Independent patch review found no additional issues. Current-head GitHub CI passed. Code Review and Security Review both completed on this head with no new findings; the bot recorded a positive result. The three original review threads were addressed and resolved.Delivery requires current-head native code-owner approval. Product callers preserve their existing required baseline, bootstrap the inert wrapper through normal protected delivery, then verify main-push and subsequent target-PR provenance before registering the additional required check. No deployment, model execution or automatic merge activation is added.