Repository navigation
fix(ci): validate backports with mergedAt - #17006
christian-byrne wants to merge 1 commit into
Conversation
|
Warning Review limit reachedNext included review available in 9 minutes. View limit detailsLimit details: You’ve used all 4 included reviews currently available. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Team Run ID: 📒 Files selected for processing (2)
Comment |
🎭 Playwright: ✅ 1908 passed, 0 failed📊 Browser Reports
|
|
this collides with #16992, which fixes the same the test here makes it order-sensitive rather than a plain conflict: #16992 also covers the second call site in |
Codecov Report✅ All modified and coverable lines are covered by tests. @@ Coverage Diff @@
## main #17006 +/- ##
==========================================
+ Coverage 81.24% 82.81% +1.56%
==========================================
Files 2464 2046 -418
Lines 126963 119485 -7478
Branches 33863 30204 -3659
==========================================
- Hits 103148 98947 -4201
+ Misses 23300 20358 -2942
+ Partials 515 180 -335
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Summary
Restores manual PR backport dispatches by querying the supported
mergedAtfield instead of the unsupportedmergedfield.Changes
mergedAt; add a workflow regression test that rejects--json merged.Review Focus
Confirm manual dispatch reports inaccessible, unmerged, and merged PRs distinctly.
Red-main evidence: https://github.com/Comfy-Org/ComfyUI_frontend/actions/runs/33892240975/job/101086446967