feat(ci): reusable workflows 加 Harden-Runner egress audit + scorecard - #2
Conversation
|
Warning Review limit reached
Next review available in: 3 minutes Limit details: You’ve used all 3 included reviews currently available under your plan. 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: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
Comment |
内容
决策依据:ADR-0011(https://github.com/Cloudbird-Software/agent-registry/pull/6)
切 block 时的起点 allowlist(audit 约 2 周后按日志收敛)
生效说明
本仓 ci.yml 是内联副本,PR 自身检查不执行新 step;合并 + bump v1 标签后由调用方(template-service 等)实际生效。
依赖顺序
依赖 .github 的 allowlist PR 先合并并 apply——否则 bump v1 后调用方 CI 会因 action 未放行而失败。