ci: delete docs-quality workflow - #556
Conversation
|
Warning Review limit reached
More reviews will be available in 39 minutes and 39 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
✨ 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 |
docs/skills/ is agent memory, not product artifacts. None of the four checks (frontmatter, line count, INDEX coverage, INDEX soundness) affect the OCI image — they enforce agent self-improvement conventions that are now explicitly documented as non-CI-gated in AGENTS.md. Deleting this workflow removes a hard gate that blocked two PRs this session for trivial doc formatting reasons unrelated to the product. Assisted-by: claude-sonnet-4-5 via pi
3c66230 to
4a59dad
Compare
Problem
docs-quality.ymlblocked two PRs this session for skill file frontmatter — zero relationship to the OCI image product.Root cause (from principal + QA review)
AGENTS.md used identical imperative language for product gates and process conventions. Agents correctly implemented both as
exit 1checks. The spec was wrong, not the agents.None of the four checks affected the product:
What changed
docs-quality.ymldeletedAGENTS.md+agentic-model.mdupdated with explicit gate taxonomy (pushed directly to main per doc-only exception): a check earnsexit 1only if failure means a broken image shipsWhat stays
The checks that actually protect the product remain untouched: dconf parity, shellcheck on shipped binaries, image ref pinning, submodule cleanliness, pre-commit, just check.