Add zizmor integration - #15
Conversation
|
Warning Review limit reached
Next review available in: 47 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. 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: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThe repository adds zizmor workflows and linting, documents workflow permissions, prevents release cancellation, and configures dependency and package release cooldowns. Tests validate workflow delegation, audit settings, cooldown values, exclusions, and release configuration. ChangesAutomation hardening
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
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 |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
This pull request introduces a new security linting workflow using zizmor, improves documentation and test coverage for this workflow, and aligns Dependabot cooldown policies with the workspace configuration. It also adds clarifying comments to workflow permissions and enhances consistency across workflow files. The most important changes are grouped below.
Security linting and workflows:
shared-zizmor.ymlfor blocking security linting of GitHub Actions and Dependabot configuration, using the zizmor action with strict settings. This workflow is now included in both the main workflows directory and the workflow examples. (.github/workflows/shared-zizmor.yml,.github/workflows/zizmor.yml,.github/workflows-examples/shared-zizmor.yml,.github/workflows-examples/zizmor.yml) [1] [2] [3]pnpm lint-actionsscript, its requirements, and how to use the new zizmor workflow. (README.md,.github/workflows-examples/README.md) [1] [2] [3] [4] [5]Dependabot and release policy alignment:
dependabot.ymlfiles to addcooldownsections for npm and GitHub Actions, matching the pnpm workspace'sminimumReleaseAgeand exclusion list. (.github/dependabot.yml,.github/workflows-examples/dependabot.yml) [1] [2] [3] [4]Test coverage and validation:
internal/gha/src/workflows.test.ts) [1] [2] [3]Workflow clarity and consistency:
.github/workflows/release.yml,.github/workflows/shared-release.yml,.github/workflows/codeql.yml,.github/workflows/shared-codeql.yml,.github/workflows/scorecard.yml,.github/workflows/shared-scorecard.yml,.github/workflows-examples/release.yml,.github/workflows-examples/codeql.yml,.github/workflows-examples/scorecard.yml) [1] [2] [3] [4] [5] [6] [7] [8] [9]These changes collectively strengthen CI security, enforce repository policies, and improve maintainability and clarity for contributors.