Conversation
mislav
approved these changes
Jan 25, 2021
Contributor
mislav
left a comment
There was a problem hiding this comment.
Thanks; looks good!
Should we add a code comment noting that the backwards-compatible fallback should be removed in a future major release?
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
2 participants
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.
This PR restores the magical renaming behavior of an existing
originremote when forking a parentrepo that already exists locally. Now, the renaming only triggers if the command is not running
attached to a TTY, preserving backwards compatibility with this command's behavior in a scripting
scenario.