ci: replace Super-Linter with reusable quality and security workflows, group Dependabot updates, and refresh scaffolded linter and Gitleaks configs.#13
Conversation
…, group Dependabot updates, and refresh scaffolded linter and Gitleaks configs.
|
Warning Review limit reached
Next review available in: 49 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: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR replaces the super-linter GitHub Actions workflow with new reusable quality and security workflows, expands linter configuration exclusions (codespell, editorconfig-checker, gitleaks) in both root and metadata locations, adds Prettier configuration/ignore files, groups Dependabot updates, and updates README, CHANGELOG, and composer.json accordingly. ChangesQuality and security CI overhaul
Estimated code review effort: 2 (Simple) | ~12 minutes Sequence Diagram(s)sequenceDiagram
participant Contributor
participant GitHubActions
participant QualityWorkflow
participant SecurityWorkflow
Contributor->>GitHubActions: push or pull_request
GitHubActions->>QualityWorkflow: reuse quality.yml@v2.0.1 with linter inputs
GitHubActions->>SecurityWorkflow: reuse security.yml with gitleaks-config and GITLEAKS_LICENSE
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
|
@codex review |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/quality.yml:
- Around line 1-32: The quality workflow currently runs on both push and
pull_request without any concurrency control, so rapid updates can queue
redundant jobs. Add a workflow-level concurrency block to
.github/workflows/quality.yml with cancel-in-progress enabled so only the latest
run for the same branch or PR continues. Keep the change near the existing on
and jobs configuration in the quality workflow.
In @.github/workflows/security.yml:
- Around line 1-19: The security workflow can queue duplicate runs because the
security job is triggered by both pull_request and push without any concurrency
control. Update the security workflow to add a concurrency group (similar to
quality.yml) so repeated pushes or PR updates cancel in-flight runs for the same
branch or PR. Use the existing security job/workflow definition in security.yml
as the place to add the concurrency setting.
In `@composer.json`:
- Around line 38-43: The composer allow-plugins entry for
yii2-extensions/scaffold is currently allow-listed without a matching
dependency. Update composer.json by either adding yii2-extensions/scaffold to
require-dev if the vendor/bin/scaffold workflow is needed, or remove the
allow-plugins entry if it is not used. Keep the config section and dependency
declarations in sync so the plugin setting reflects an actual installed package.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: fdbbb275-5151-44a8-9767-8987e621154f
📒 Files selected for processing (18)
.github/dependabot.yml.github/linters/.codespellrc.github/linters/.editorconfig-checker.json.github/linters/.gitleaks.toml.github/workflows/linter.yml.github/workflows/quality.yml.github/workflows/security.yml.gitignore.prettierignore.prettierrc.jsonCHANGELOG.mdREADME.mdcomposer.jsonmetadata/.github/linters/.codespellrcmetadata/.github/linters/.editorconfig-checker.jsonmetadata/.github/linters/.gitleaks.tomlmetadata/.github/linters/actionlint.ymlmetadata/.prettierignore
💤 Files with no reviewable changes (4)
- .github/workflows/linter.yml
- metadata/.github/linters/actionlint.yml
- .github/linters/.gitleaks.toml
- metadata/.github/linters/.gitleaks.toml
📜 Review details
🔇 Additional comments (15)
.github/dependabot.yml (1)
5-25: LGTM!.gitignore (1)
1-4: LGTM!.github/linters/.codespellrc (1)
2-2: LGTM!.github/linters/.editorconfig-checker.json (1)
3-7: LGTM!metadata/.github/linters/.codespellrc (1)
2-2: LGTM!metadata/.github/linters/.editorconfig-checker.json (1)
3-7: LGTM!.prettierrc.json (1)
1-22: LGTM!.prettierignore (1)
1-33: LGTM!metadata/.prettierignore (1)
1-21: LGTM!.github/workflows/quality.yml (2)
17-32: LGTM!
8-19: 🔒 Security & PrivacyNo change needed
contents: readmatches the reusable workflow’s requirement.CHANGELOG.md (1)
10-11: LGTM!README.md (1)
42-42: LGTM!Also applies to: 90-93, 113-116
composer.json (1)
15-17: LGTM!.github/workflows/security.yml (1)
8-19: 🔒 Security & Privacy
contents: readis sufficient here. The reusablesecurity.ymlworkflow is documented to run with minimal permissions, sopull-requests: writeisn’t needed for gitleaks PR comments.> Likely an incorrect or invalid review 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: c87f51a8dd
ℹ️ 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".
terabytesoftw
deleted the
ci/replace-super-linter-refresh-metadata-scaffold
branch
1 participant
Pull Request