[
https://issues.apache.org/jira/browse/KAFKA-2328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629856#comment-14629856
]
Ismael Juma commented on KAFKA-2328:
------------------------------------
[~guozhang], that's true. I just looked at the code and it looks like it's by
design, no action is taken after the "Resolving JIRA" step. I am guessing that
the idea is to leave you on the branch that was pushed in case you want to look
at it (although it's not clear to me why one would need this, particularly if
the branch has been pushed).
What option do people prefer:
# Leave as is
# Checkout the branch the user was in before the script was executed
# Checkout trunk
> merge-kafka-pr.py script should restore previous branch after merge is
> cancelled
> --------------------------------------------------------------------------------
>
> Key: KAFKA-2328
> URL: https://issues.apache.org/jira/browse/KAFKA-2328
> Project: Kafka
> Issue Type: Improvement
> Reporter: Ismael Juma
> Priority: Minor
>
> [~gwenshap] asked:
> "If I start a merge and cancel (say, by choosing 'n' when asked if I want to
> proceed), I'm left on a detached branch. Any chance the script can put me
> back in the original branch? or in trunk?"
> Reference
> https://issues.apache.org/jira/browse/KAFKA-2187?focusedCommentId=14621243&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14621243
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
