fix(ci): repair release eligibility GraphQL query - #67
Conversation
Move the policy query into a readable GraphQL document so its structure is reviewable and the workflow can load it fail-closed. Add focused coverage for delimiter balance, workflow wiring, and every pagination boundary used by the fail-closed classifier.
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (3)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. WalkthroughThe release workflow now reads its GraphQL eligibility query from a dedicated file. New tests validate the query structure, workflow wiring, and pagination metadata. ChangesRelease eligibility query
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The release workflow now loads its eligibility query from a checked-in file while preserving fail-closed pagination checks. No concrete merge-blocking issue is evidenced. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 33.33% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files. (2 skipped: 2 unsupported.)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 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 |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Summary
Validation
python3 -m pytest -q tests/test_release_eligibility.py tests/test_release_eligibility_query.py— 9 passedgit diff --checkScope
Fixes the current parser error before the CLI release-eligibility decision. This PR does not change labels, create tags/releases, or publish artifacts. The extension-side handoff is tracked separately in WildestAI/wildest-vscode-ext#51.
Fixes #53
Summary by CodeRabbit
Refactor
Tests