Proposal: branch.<name>.remotepush
- From
Ramkumar Ramachandra <artagnon@gmail.com>
- Date
- Feb 7, 2013, 16:14 UTC
- Message-ID
- <CALkWK0nA4hQ0VWivk3AVVVq8Rbb-9CpQ9xFsSOsTQtvo4w08rw@mail.gmail.com>
Hi,
This has been annoying me for a really long time, but I never really got around to scratching this particular itch. I have a very common scenario where I fork a project on GitHub. I have two configured remotes: origin which points to "git://upstream" and mine which points to "ssh://mine". By default, I always want to pull `master` from origin and push to mine. Unfortunately, there's only a branch.<name>.remote which specifies which remote to use for both pulling and pushing. There's also a remote.<name>.pushurl, but I get the feeling that this exists for an entirely different reason: when I have a server with a highly-available read-only mirror of the repository at git://anongit.*, and a less-available committer-only mirror at ssh://*.
How about a branch.<name>.remotepush that specifies a special remote for pushing, falling back to branch.<name>.remote?
Ram