Repository navigation
GH#34293: docs: keep Qlty on organisation repos and skip its out-of-minutes check - #34294
Conversation
|
Important Review skippedAuto reviews are limited based on label configuration. 🏷️ Required labels (at least one) (1)🚫 Excluded labels (none allowed) (1)
Please check the settings in the CodeRabbit UI or the ⚙️ Run configuration
You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
Markdown Lint (changed-line scoped)No new violations in changed lines (0 pre-existing in touched files — ignored).
|
Up to standards ✅🟢 Issues
|
Shell Function Complexity Regression Gate✅ No regression — no new function(s) >100 lines.
|
Qlty Smell Regression Gate✅ No change — smell count unchanged.
|
🔍 Code Quality Report�[0;35m[MONITOR]�[0m Code Review Monitoring Report SonarCloud: 0 bugs, 0 vulnerabilities, 1 code smells Sat Oct 10 22:58:46 UTC 2026: Code review monitoring started 📈 Current Quality Metrics
Generated on: Sat Oct 10 23:01:18 UTC 2026 Generated by AI DevOps Framework Code Review Monitoring |
Shell Nesting Depth Regression Gate✅ No regression — no new file(s) with nesting depth >8.
|
File Size Regression Gate✅ No regression — no new non-README Markdown file(s) >1000 lines at root / >500 elsewhere.
|
What
Repository setup and management guidance now says what the merge tooling already does. On organisation (and private) repositories, Qlty's GitHub App runs out of minutes each month. The out-of-minutes "qlty check" is billing: skip it, keep the app, and never make it a required check.
.agents/reference/ci-gate-policy.mdrule 14: the minutes return monthly, so keep the app installed (not a reason to remove Qlty); never require "qlty check" on a limited repository; points toqlty.md..agents/tools/code-review/qlty.md: Quick Reference bullet and a "GitHub App: monthly minutes" section for setup and management. It covers keeping the app, skipping the failure, never requiring it, real findings still counting, and the split between the app's check and CLI-based CI gates. It names the helpers that already skip it (gh-checks-wait-helper.shapply_qlty_billing_policy,pulse-merge-required-checks.sh_pmrc_repo_has_qlty_credit_limit)..agents/tools/code-review/setup.md: Qlty row in the platform table, the rule in one line, and a troubleshooting row for "out of minutes"..agents/tools/wordpress/wp-plugin-new.md: an out-of-minutes qlty check still proves Qlty is connected; skip it, never remove Qlty.Why: in an owner session, an agent read a red out-of-minutes qlty check as a reason to remove Qlty from an organisation. It edited four repositories' docs and asked the owner to uninstall the app, when the owner's policy is to keep it for the free monthly minutes. Merge-time behaviour was already right; only the setup guidance lacked it.
Verification
npx markdownlint-cli2on the four files: 0 issues.rg -n 'rule 14' .agents/tools/code-review/qlty.md .agents/tools/code-review/setup.md .agents/tools/wordpress/wp-plugin-new.md: a pointer in each.Resolves #34293
aidevops.sh v3.39.1 plugin for OpenCode v1.18.35 with claude-opus-5-5