Yes, if it's two different websites, there's no point in them sharing a
repository. Have two repositories: website-us and website-uk.
There's nothing wrong with having more machines involved, of course. You can
clone around the repository as many times as you want.
But before a developer in Hawaii can push to the US webserver, he needs to
get up to date first (pull in, or rebase the changes others have made on the
You can set up a hook in the server repositories, more specifically a
It's not bad practice, I think :)
Here's the link again, the key word is *git archive*:
You received this message because you are subscribed to the Google Groups "Git
for human beings" group.
To post to this group, send email to email@example.com.
To unsubscribe from this group, send email to
For more options, visit this group at