fork: Rename 'origin' to 'upstream' after forking #553
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
|
@nicolaiskogheim This time the trigger was bit slower ;) |
| git clone "https://github.com/$user/$project" "$project" | ||
| if [ "$origin" = true ]; then | ||
| git remote rename origin upstream | ||
| git remote add origin "https://github.com/$user/$project" |
There was a problem hiding this comment.
We need to do a git fetch --all here to update the references and make the new origin "visible" so to speak.
There was a problem hiding this comment.
Isn't git fetch origin enough?
I have several remote refs and some of them are accessible only in my office. I'm afraid that git fetch --all causes some kind of network error in my home.
|
@nicolaiskogheim I ran |
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.
Improve #552.