feat(ci): run issue lifecycle audit - #477
Conversation
|
Warning Review limit reached
Next review available in: 13 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c46dacc127
ℹ️ 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".
c46dacc to
d18145a
Compare
2c30f42 to
e76ab42
Compare
Issue relationship
Closes #467
Change contract
Run the existing lifecycle auditor as the stable, read-only
Issue Lifecycle Auditcheck from the trusted default branch for pull requests and scheduled/manual repository audits.Out of scope
Required-check enforcement (#460), PR-head status invalidation after linked-issue edits (#480), historical metadata reconciliation (#459), lifecycle policy changes, issue/PR/label/status mutations, runtime deployment, research logic, and trading behavior.
Dependency / merge order
PR #470 / issue #458 merged first. This branch is rebased on
3aae5ddc7c2a699c3d1b6ff95b1f322f6b8bd7e9; #480 exclusively owns and must canary the authoritativeIssue Lifecyclestatus before #460 enables that required context; this PR intentionally emits onlyIssue Lifecycle Audit.Focused validation
pull_requestand a workflow that did not validate proposed YAMLIssue Lifecyclejob name before the workflow adoptedIssue Lifecycle Auditruby -c .github/scripts/test-issue-lifecycle-workflow.rb— PASSruby .github/scripts/test-issue-lifecycle-workflow.rb— PASSruby .github/scripts/test-issue-lifecycle-workflow.rb .github/workflows/issue-lifecycle.yml— PASSruby -c .github/scripts/issue-lifecycle-audit.rb— PASSbash .github/scripts/test-issue-lifecycle-audit.sh— PASSactionlint .github/workflows/issue-lifecycle.yml— PASSgit diff --check origin/main...HEAD— PASSRollout / rollback impact
Adds the read-only
Issue Lifecycle Auditcheck but does not make it required. Pull-request runs usepull_request_target, execute only default-branch code, fetch the proposed workflow YAML as data, and parse it with the trustedYAML.safe_loadcontract test before auditing the current PR. Scheduled/manual runs audit live repository metadata and write the result to the step summary. Rollback is a normal revert and does not mutate GitHub issues, statuses, or repository settings.