This repository has been archived by the owner on Nov 28, 2023. It is now read-only.
Specifying ORIGIN on 'git remote update'. #70
Merged
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
stuartherbert
added a commit
that referenced
this pull request
Jan 17, 2014
Specifying ORIGIN on 'git remote update'.
|
Merged. Thanks. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Github, Bitbucket, etc. are typically used as origin and they're fast but production and staging servers can be slow (especially Heroku). They also don't contain feature/hotfix branches in the Gitflow workflow.
The constant fetching of my staging and production servers was just a consistant minor annoyance.