Replace --push option with asking whether to push to remote
#186
Conversation
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
geofflamrock
changed the title
--push option with asking whether to push to remote
Merged
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.
As part of #165 a new
--pushoption was added to thenewandbranch newcommands to push the newly created branch to the remote repository. The default was also changed on the command to not do this to better support offline operations.This is proving to be a pain, I always forget to add
--pushand then need to runstack pushall the time. So this PR instead asks if you want to push the new branch to the remote to make it easier, removing the--pushoption altogether. I might replace it at some point as part of adding support for non-interactive workflows.