chore(ci): label FTC-closed PRs as needs-issue - #7249
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (4)
🚧 Files skipped from review as they are similar to previous changes (4)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe first-time contributor workflow now adds the ChangesFirst-time contributor issue enforcement
Merge Risk: ⚪ Minimal · up to The workflow now labels and closes first-time contributor pull requests without a valid open issue reference, with accompanying documentation and regression coverage. No current merge-blocking risk is identified. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Full details: Docstring CoverageExplanation Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 2 functions across 1 files. (3 skipped: 3 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 |
|
Note GitHub couldn't provide a complete incremental comparison for this pull request, so CodeRabbit is performing a full review instead. This review may take a little longer. |
Related issue
N/A — follow-up to the first-time contributor issue gate.
Summary
needs-issuelabel oncrewAIInc/crewAI.issuespermission towriteso labeling works on closed PRs.Verification
uv run pytest lib/crewai/tests/ci/test_ftc_require_issue.py)Additional context
Filter auto-closed FTC PRs with
is:pr is:closed label:needs-issue.