As Matt points out, branches are a wonderful thing. I can certainly understand keeping the master branch "production ready", but why wouldn't you want them to push branches up? --tek
On Thu, Oct 16, 2008 at 10:54 AM, Matt Todd <[EMAIL PROTECTED]> wrote: > > Szymek, > > You can push up branches to create remote branches. This is a great > way to store in-development changes that *will* get merged back into > master, and makes sharing the code trivial. > > Here's a quick article about it with very detailed information: > > http://www.zorched.net/2008/04/14/start-a-new-branch-on-your-remote-git-repository/ > > Essentially, in the local branch you want to push up to be remote, do this: > > git push origin local_branch_name:refs/heads/remote_branch_name > > You can then checkout a remote branch and keep them bound tightly with: > > git checkout --track -b remote_branch_name origin/local_branch_name > > Cheers, > > Matt > > > > On Thu, Oct 16, 2008 at 12:37 PM, szimek <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > this question is not github related, but I couldn't find any other > > active git-only related forum. > > > > Currently we got a single public main git repository and few > > developers working in small teams on a project.The code in our public > > repo in the master branch is considered as "production ready". > > > > The problem is i.e. when someone does some experimenting and makes > > some cool new feature. How can others verify the changes he made? I > > don't want him to push this change into our main repo, others can't > > pull from his local repository and he can't push to theirs. Or maybe > > someone's doing a total rewrite of the app that takes lots of time and > > wants to be able to access the code from any computer or to be able to > > store his code on remote server just in case he losts his laptop or > > whatever. > > > > So we thought about setting up a public repo for every team. But how > > would then pushing changes into the main public "production ready" > > repo would look like? Do I have to create another working copy only > > for preparing the code for production, where I'd pull changes from all > > public dev repos, test them and then push the code into the main repo? > > > > Maybe a better idea would be to make branches for each team in the > > main repo instead of creating public repos? > > > > Any suggestion? > > > > Cheers, > > Szymek > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "GitHub" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/github?hl=en -~----------~----~----~----~------~----~------~--~---
