Thank you, Marcel and Sam,

Sorry for the late response. I've been busy studying Git!

I did end up with a similar solution to what you guys suggested, and it 
seems to be working so far. I realized that there was no real 
need/advantage to using Github's "Fork" button when using private repos and 
for our own projects. So, I simply copied the entire local repo and changed 
the URL to the remote repo in the local config file, and then push it up to 
a new/empty Github repo. So, each website has two repos (a local repo and a 
remote one on Github), and each local repo is connected to two repos on 
Github (one to the original "official" repo and the other is to its own 
repo). This way, I can propagate global changes from the "official" repo. 
With this set-up, we are able to share each website project with other team 

This setup is definitely better than my SVN setup; it's more flexible. I'm 
surprised that Github doesn't allow you to fork your own project. One of 
the strengths of Git is its ability to develop projects in parallel, and 
this certainly comes in handy when you have to develop multiple similar 
websites in parallel. I don't see why Github should discourage people from 
developing multiple projects of *their own* in parallel. Hopefully they'll 
remove that limitation in the future.

Thanks again,

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to