feat(merge): make merge asynchronous via runway#247
Draft
behinddwalls wants to merge 1 commit into
Draft
Conversation
This was referenced Jun 16, 2026
behinddwalls
force-pushed
the
preetam/merge-async
branch
from
92d1ef3 to
f89fcb9
Compare
behinddwalls
force-pushed
the
preetam/mergeconflict-async
branch
2 times, most recently
from
2ee27cf to
a970815
Compare
behinddwalls
force-pushed
the
preetam/merge-async
branch
from
f89fcb9 to
2b21765
Compare
behinddwalls
force-pushed
the
preetam/mergeconflict-async
branch
from
a970815 to
bc59a27
Compare
behinddwalls
force-pushed
the
preetam/merge-async
branch
from
2b21765 to
cd3ef63
Compare
behinddwalls
force-pushed
the
preetam/mergeconflict-async
branch
from
bc59a27 to
d9dc61f
Compare
behinddwalls
force-pushed
the
preetam/merge-async
branch
from
cd3ef63 to
2d17620
Compare
behinddwalls
force-pushed
the
preetam/mergeconflict-async
branch
from
d9dc61f to
7ab64d3
Compare
behinddwalls
force-pushed
the
preetam/merge-async
branch
from
2d17620 to
4a525e5
Compare
Rework the merge stage from a synchronous in-process pusher call into a runway round-trip, mirroring the merge-conflict check. The merge controller now builds a full runway MergeRequest from the batch's member requests (one MergeStep per request, in Contains order) and publishes it to the runway-owned merger queue, keyed by the batch id as the correlation id. A new mergesignal controller consumes the MergeResult off merger-signal, transitions the batch to Succeeded/Failed, and fans out to conclude and speculate; a mergesignal DLQ reconciler fails the batch on an unprocessable result. The in-process pusher extension is retired from the orchestrator wiring (left in-tree but unused, like mergechecker); removal is a follow-up. workflow.md and extension-contract.md updated to reflect both the check and the merge crossing into runway over the shared MergeRequest/ MergeResult contract. Co-authored-by: Cursor <cursoragent@cursor.com>
behinddwalls
force-pushed
the
preetam/mergeconflict-async
branch
from
7ab64d3 to
b6042a6
Compare
behinddwalls
force-pushed
the
preetam/merge-async
branch
from
4a525e5 to
288e995
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rework the merge stage from a synchronous in-process pusher call into a
runway round-trip, mirroring the merge-conflict check. The merge
controller now builds a full runway MergeRequest from the batch's member
requests (one MergeStep per request, in Contains order) and publishes it
to the runway-owned merger queue, keyed by the batch id as the
correlation id. A new mergesignal controller consumes the MergeResult off
merger-signal, transitions the batch to Succeeded/Failed, and fans out to
conclude and speculate; a mergesignal DLQ reconciler fails the batch on
an unprocessable result.
The in-process pusher extension is retired from the orchestrator wiring
(left in-tree but unused, like mergechecker); removal is a follow-up.
workflow.md and extension-contract.md updated to reflect both the check
and the merge crossing into runway over the shared MergeRequest/
MergeResult contract.
Co-authored-by: Cursor cursoragent@cursor.com
Test Plan
Issues
Stack