-
-
Notifications
You must be signed in to change notification settings - Fork 60
When cherry_picker fails, drop you off in the checkout #51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sorry about that.. yeah it's definitely something that I need to address. Maybe related to #45 too |
@Mariatta Nothing to apologize for! Tool worked out great (only issue is GitHub seems to keep thinking I might want to create a PR for the 3.5 branch)! |
If we did decide to do this (and I think it's reasonable for the interactive case), it would be helpful if it printed two things before exiting:
|
Hmm.. I couldn't figure out how to actually |
Once #99 is merged, this is not needed anymore since the people will be cherry-picking from cpython directory. |
I just had a cherry-pick fail, but because I was running
cherry_picker
from its own git repo it took me a minute to realize that I couldn't find the failed branch because I had notcd cpython
yet. It might work out better to automaticallycd
into the checkout upon failure (with an appropriate message that this was done).The text was updated successfully, but these errors were encountered: