"sparo fetch" behaves the same as "git fetch" when no remote or no branches specified #81
Conversation
This file contains 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.
Basic Checks
Have you run
rush changefor this change?If No, please run
rush changebefore, this is necessary.If adding a new feature, the PR's description includes:
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
Summary
"sparo fetch" behaves the same as "git fetch" when no remote or no branches specified
Detail
Right now,
sparo fetch originwill be treated asgit fetch origin <current_branch>. This doesn't follow the same behavior asgit fetchdoes. This PR fixes it and get aligned withgit fetchHow to test it