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 59 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 |
|
Security review (Opus) at e968902: approve.
Policy decision (merger): option (a), the per-file EXEMPT for Pre-existing items, not this PR`s, filed as #18468:
Queued for the next merge train. |
✅ SSOT Configuration Compliance: Passing🎉 No new hardcoded values of either class — Known backlog in |
Thinking Path
Carried from three stale local branches (
issue-15411-github-api-module,issue-12984-pr-comment-upsert,issue-18158-tooling-clones) under the owner rule "any sitting branch must be linked to a finished PR" (branch cleanup 2026-10-12). All are CI/pipeline tooling. Built fresh from currentmain, with only each branch's unique commits cherry-picked; no stale tree was revived.What Changed
GitHubApiis extracted frompipeline-scripts/ci_dispatch_watchdog.pyintopipeline-scripts/github_api.py. The three importers (ci_dispatch_retry.py,ci_red_cause.py,release_sync_main.py) use it.rerun_runandrate_limit_remainingmove ontoGitHubApitoo.github_api.py, with the total unchanged..github/actions/upsert-pr-comment/, that is marker-based and paginated.ssot-coverage.ymlandai-security-review.ymluse it, and the inline upsert is removed. ci(perf): collapse 15 duplicate paths-filter jobs into one reusable workflow #15360's changes toai-security-review.ymlare kept; only the upsert step differs. The five fire-and-forget comment callers are untouched.env_registry_testing.pyandENV_VARS.mdgain one row.tools/schema-split/schema_rules.py(one rule set for the schema-split tools);scripts/drift_cli.py(one drift CLI);tools/schema-split/resolve_schema_conflicts.pyuses the shared logging, with noprint(.repo_tests/egress_default_guard_17576_test.pyEXEMPTgains.github/actions/upsert-pr-comment/upsert_pr_comment.py.urlopenas guarded..github/tree out of the AutoBot-runtime egress census, say so.Verification
repo_tests/_reach_policy.pyandreach_scope_claim_17844_test.py(hub files), where main's entries are kept plus each commit's own.ai-security-review.yml, ci(perf): collapse 15 duplicate paths-filter jobs into one reusable workflow #15360 (0a3d672) is kept.egress_default_guard_17576+reach_declarations+reach_scope_claim_17844+ the size ratchet: 738 passed.actionlint, which isn't installed locally; CI runs the workflow lint.Risks
Model Used
Anthropic Claude Opus 5.5 (claude-opus-5-5), coordinating. Anthropic Claude Sonnet 5.5 (claude-sonnet-5-5) subagent for the cherry-picks and verification.
Issue Link
Closes #18170
Refs #15411
Refs #12984
Refs #18158
Still open:
CAUSE_*→StrEnumitem;.github/workflows/duplication-guard.yml~:94, 11707) needs a jscpd measurement, which can't run locally while tooling(slm-frontend): the shared SLM node_modules was emptied and now holds a link to itself — every worktree's SLM vue-tsc and vitest are dead #18406 is open.Single-issue rationale: one CI-tooling scope carried from three stale branches. Only #18170 is fully delivered; the other three are partial and stay open, as listed above.
Changelog fragment