[SYMPP-FF99] Make merged PR projection agree with delivery truth - #627
Conversation
Summary: - supersede stale nested PR merge state from pr_merged delivery - preserve provider merge state for non-terminal work packages Rationale: - the PR signal and nested PR projection must use the same delivery truth - avoid new persisted state or provider refresh behavior Tests: - mix test test/symphony_elixir/symphony_plus_plus/dashboard/work_request_delivery_projection_test.exs - make -C elixir all Co-authored-by: Codex <codex@openai.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan includes up to 3 reviews per rolling hour; 2 remain after this review. 📝 WalkthroughWalkthroughThe delivery board now passes delivery context into pull request summary generation. Recorded ChangesDelivery-aware pull request summaries
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The change aligns nested pull-request merge state with explicit merged delivery truth while preserving provider-derived state for non-terminal deliveries; no actionable merge-blocking risk remains after normal checks and review. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Context
Terminal
pr_mergeddelivery made the PR signal say merged while nested historicalpr.merge_statecould still say open or blocked.TL;DR
Use recorded merged delivery truth when projecting nested PR merge state.
Summary
pr_mergeddelivery.Alternatives
Test Plan
make -C elixir allmake -C elixir ci-fullwhen release/full validation is requiredmix test test/symphony_elixir/symphony_plus_plus/dashboard/work_request_delivery_projection_test.exsrvw_a66bb533Summary by CodeRabbit