fix(ci): preserve high-risk auto-resolve routing across renames#873
Conversation
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
|
Warning Review limit reached
Next review available in: 6 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Codex auto-resolve workflow recognizes additional high-risk paths and evaluates current and previous filenames for renamed files. Its validation guard and tests were updated, and the branch review ledger gained a record. ChangesCodex routing
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant GitHub as GitHub PR file metadata
participant Workflow as GitHub Actions workflow
participant Patterns as Risk routing checks
participant Codex as Codex request
GitHub->>Workflow: Provide current and previous filenames
Workflow->>Workflow: Normalize candidate paths
Workflow->>Patterns: Check exclusion, high-risk, and source patterns
Patterns-->>Workflow: Return route reasons
Workflow->>Codex: Send auto-resolve request when routed
Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4fb9bf9e29
ℹ️ 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 resolve actionable Codex review findings for this pull request and current head using the repository instructions. This is the pull request's single automatic repair pass: do not perform a fresh review, create new standalone findings, or request another review. Work only the existing unresolved Codex threads on the current head. Always fix P0 and P1 findings. For P2 and lower findings, fix only clear, scoped, low-risk issues; otherwise disposition them with a concise reason. After fixing or dispositioning a thread, reply in that thread with as the first line, followed by a concise summary; that marker authorizes the workflow to close that exact thread. If human input or new authorization is required, do not use the marker and leave the thread open with the blocker. Finish only after every actionable thread is fixed or dispositioned and closed, or explicitly left open for a human decision. Do not update the branch from main, address unrelated reviews, broaden scope, or create more than one scoped fix commit. Do not use external APIs, paid services, credentials, dependency changes, or broad refactors unless explicitly authorized. Add targeted tests where behavior changes and run the narrowest relevant validation. |
|
@copilot resolve the merge conflicts on this branch. |
…diation-pr-0a27 # Conflicts: # docs/branch-review-ledger.md
|
Summary
PR / Commit
Testing
|
Head branch was pushed to by a user without write access
Merged ... All actionable Codex review findings were already resolved before this pass. The single P2 thread (excluded rename history triggering high-risk routing) was fixed in |
Summary
filenameandprevious_filenamewhen routing renamed pull-request files.src/data, reusable GitHub actions, and the action-pin/Codex guard scripts as high-risk repository infrastructure.The broader audit remediation was already on
mainthrough #814. This PR contained only the residual routing fix and its verification record.Verification
npm run verify:pr-localnode C:\Dev\Apps\Database\node_modules\vitest\vitest.mjs run tests/codex-autofix-workflow.test.ts tests/github-action-pins.test.ts --reporter=dot— 2 files / 54 tests passed.node scripts/check-codex-autofix-workflow.mjsnode scripts/check-github-action-pins.mjsgit diff --checknpm run verify:ui— not run; no UI, routing, styling, browser, or accessibility behavior changed.npm run verify:release— not run; disproportionate for a workflow-only change and may include provider-backed gates.Review resolution
routeableFilePathsfirst and using it for both risk and source-complexity checks.Risk and rollout
ebb8c90ca.Clinical Governance Preflight
Not applicable: no ingestion, retrieval, answer generation, clinical output, source rendering, privacy, document access, or production environment behavior changed.
Notes
ebb8c90ca; all four changed blobs were verified equal between the reviewed head and freshorigin/main.