Repository navigation
respect GH_HOST when resolving remotes - #2301
Merged
Merged
Conversation
mislav
suggested changes
Nov 17, 2020
mislav
left a comment
mislav
left a comment
Contributor
There was a problem hiding this comment.
Thanks for taking this on!
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.
closes #1668
This pull request notices when GH_HOST has been set and then only resolves local remotes that match the set hostname. With this in place, a heterogeneous mix of hosts in a local remote file will not cause GH_HOST to be ignored.
An error is returned if the hostname specified in GH_HOST is not present in the local remotes.