Jeff King <[email protected]> writes:
> But here you do not have a pushurl defined in the first place. So I
> guess this is really just a shortcut for swapping the two, like:
>
> git remote set-url --push gh $(git config remote.gh.url)
> git remote set-url gh new-fetch-url
It seems that this swapping is only necessary because the repository
is set up in this way:
$ browser github.com
... fork upstream to your own publishing repository ...
$ git clone <your publish repo>
... oops, I am set up to fetch from myself ...
$ git remote set-url --push mine <url for your publish repo>
$ git remote set-url <url for your upstream repo>
If you are fetching from somebody else and then pushing into your
own publishing repository (i.e. fork of that upstream), why isn't
the sequence of event like this, instead?
$ git clone $upstream
$ browser github.com
... fork upstream to your own publishing repository ...
$ git remote set-url --push mine <url for your publish repo>
Isn't this one of those bad workflows encouraged by GitHub, for
which you guys have to be punished ;-)?
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
