Hacker News Reader

Comment by aprescott | Hacker News Reader

You know what I want? Transparent failover somehow baked into git remotes.

    you <--> (X <--> Y)

If you push to and pull from X, and X should be unavailable, automatically start using Y. When X is pushed to, check with Y first to keep in sync. There are ways to push to multiple remotes by defining multiple remote URLs, but then it's a harder problem of dealing with downtime.

View on HN

It's really easy to push to two remotes. I have a tfs service account setup and using git and also a github account. I like tfs's project and issue tracking better but want the public repo available on github.

git add remote <name> <url> git add remote <name> <url> then create a shell script that checks both remotes for the latest if one is greater than the other merge the two if they are the same then push to both. Then just always push with that script.

Just how I've handled it so far. That said a autoMagical way of handling it built into github/git itself would be cool.

As I said, it's doable with scripts and whatnot, but transparent and built into git would be awesome. I see it as something you just set up on a remote repository server. No need to make N developers aware of it, or aware of the script, or resolving the script breaking, or having a ton of implementations of said script across different teams and companies.

Doesn't help if you use GitHub for issues, of course, but hey!

Reply on news.ycombinator.com