feat(runway): wire merge controller to Merger extension#366
Closed
kevinlnew wants to merge 2 commits into
Closed
Conversation
The merge-conflict-check controller was a parse-and-log stub. Wire it to the Merger extension so it performs the dry-run check and publishes the MergeResult to the merge-conflict-check-signal topic. A merge conflict is an expected outcome (ack + publish FAILED), not an infrastructure error.
The merge controller was a parse-and-log stub. Wire it to the Merger extension so it performs the committing merge and publishes the MergeResult (with produced revisions) to the merge-signal topic. Mirrors the merge-conflict-check controller pattern.
This was referenced Jul 14, 2026
Contributor
Author
|
Closing; duplicate by accident with old branch. |
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
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
The merge controller was a parse-and-log stub. Wire it to the Merger
extension so it performs the committing merge and publishes the
MergeResult (with produced revisions) to the merge-signal topic.
Mirrors the merge-conflict-check controller pattern.
Test Plan
Issues
Stack