Git export of a single branch

views:

181

answers:

+1 Q:

Git export of a single branch

Hi,

I worked locally on a git repository. It has various branches like a dev branch, some branch for experimental changes and so on. And of course a master branch.

I want to setup a public (well, indeed it's a lan thing, better say "shared") repository to only contain the master branch.

How to export that branch so that i can copy it to the destination folder? Thanks

I'd consider setting up separate public repository with "alternates" pointing to the one you're working on and push your branch to it. Or maybe symlink the master branch to the one in your local repository. I haven't tried that, but it should work.

Michael Krelin - hacker 2010-03-03 10:36:53

+1 A:

As the git-push manual says:

git push origin HEAD:master

Push the current branch to the remote ref matching master in the origin repository. This form is convenient to push the current branch without thinking about its local name.

git push origin HEAD

A handy way to push the current branch to the same name on the remote.

Using these commands you do:

Create git init --bare repository at some "shared location"
git remote add origin this location to your current working repository
git push --force origin HEAD from your master branch
Other devs now can clone that repository with only master branch

Marcin Gil 2010-03-03 10:43:13

Oh, is OP talking about remote public repository?

Michael Krelin - hacker 2010-03-03 10:52:38

He exactly says he want's to create new repo. Doesn't matter if that's really remote or just another directory. Added some info to clarify. Thanks.

Marcin Gil 2010-03-03 11:15:41

Well, it does. If it's locally, I wouldn't like the solution you propose.

Michael Krelin - hacker 2010-03-03 13:00:33

Care to explain why? It works for me. As it is a "lan thing" then it can be that this directory will be shared over CFS/Samba or served via ssh.

Marcin Gil 2010-03-03 13:21:14

Sure it works. The drawbacks are (a) you have to push each time you commit (with alternates and symlink trick that should do automatically) and (b) it takes twice as much space, although in case of local machine could be fixed in your solution (it will turn it into a repetition of the first part of my proposal;-)). And yes, the "lan thing" of course leaves quite some room for imagination.

Michael Krelin - hacker 2010-03-04 11:44:17

Well.. In my work I only push to shared repo once a feature/bugfix/etc is ready and not every single commit that can be partial solution. As for the space requirement, well.. disks are cheap now and you gain repo separation: your own workplace and what you share with others. Moreover symlinking to your own workplace as shared place will share what you have actually checked out won't it?

Marcin Gil 2010-03-04 12:06:51

ansaurus

tags:

views:

answers:

Git export of a single branch

related questions