Repository navigation
fix(skills): read StatusContext results in deps CI gate - #40
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configuration
📒 Files selected for processing (1)
Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughGate B’s status-check filter now reads either ChangesStatus-check filtering
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to No actionable merge-blocking risk is evident; pending checks remain not-green while the filter handles both status-context and check-run fields. 🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 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 |
The Gate B jq filter in the deps skill only looked at
.conclusion. Commit status entries instatusCheckRollup(CodeRabbit, Devin Review) areStatusContextobjects that report their result in.stateand their name in.context, so every green PR showed up withnull: nullfailures.The filter now uses
.conclusion // .statefor the result and.name // .contextfor the label.Verified against the open Dependabot PRs #36–#39 (all green → empty output) and a sample rollup with a failed status context, a failed check run and an in-progress check (all three reported).
🤖
Summary by CodeRabbit