ci-merge: add --pause-on-conflict option for interactive conflict res…#8
Open
shashim-quic wants to merge 1 commit into
Open
ci-merge: add --pause-on-conflict option for interactive conflict res…#8shashim-quic wants to merge 1 commit into
shashim-quic wants to merge 1 commit into
Conversation
…olution When a topic branch merge fails, the default behaviour is to abort and exit immediately. This makes it impossible to resolve conflicts manually and continue the integration run without restarting from scratch. Add a new --pause-on-conflict (-p) flag. When set, a merge failure prints a conflict banner listing the affected files and waits for the user to type 'y' (continue) or 'n' (abort) on stdin. This lets the operator resolve conflicts in a separate terminal and resume the integration without losing the work already merged. Signed-off-by: Shiraz Hashim <shiraz.hashim@oss.qualcomm.com>
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.
…olution
When a topic branch merge fails, the default behaviour is to abort and exit immediately. This makes it impossible to resolve conflicts manually and continue the integration run without restarting from scratch.
Add a new --pause-on-conflict (-p) flag. When set, a merge failure prints a conflict banner listing the affected files and waits for the user to type 'y' (continue) or 'n' (abort) on stdin. This lets the operator resolve conflicts in a separate terminal and resume the integration without losing the work already merged.