Based on answers and comments here. You can create non-bare repo and run: git ls-files –recurse-submodules | tar caf ../prog.tar.gz -T- To handle files starting with hypen, use –verbatim-files-from To put files in folder inside the archive, use –xform s:^:prog/: Full version: git ls-files –recurse-submodules | tar caf ../prog.tar.gz –xform s:^:prog/: –verbatim-files-from -T-
Since the –shared option just sets the permissions on everything in the repository to group-writable you could do this manually later: $ chmod -R g+w the/repo/path Plus, add sharedrepository = 1 under the [core] section in .git/config. Shared repos also have the following receive option defined by default (which you may or may not want): … Read more
You can try the other command which list files: git ls-tree –full-tree -r HEAD According to this comment, the command git ls-tree works in bare repo.
You can simply clone the repository to another directory on the same machine: git clone /bare/repo/dir The current directory will become a non-bare clone of your repo, and you’ll get a checkout of the master branch automatically. Then use the usual commands like git pull to update it as needed. As a side benefit, this … Read more
A bare repository is pretty much something you only push to and fetch from. You cannot do much directly “in it”: you cannot check stuff out, create references (branches, tags), run git status, etc. If you want to create a new branch in a bare Git repository, you can push a branch from a clone … Read more
Note: I tested this on a very simple 1-commit repository. Double-check this, read the man pages, and always be happy you’ve backed up before following advice you found on StackOverflow. (You do back up, right?) To convert a –bare repository to a non-bare: Make a .git folder in the top-level of your repository. Move the … Read more
You can use the git update-ref command. To remove the last commit, you would use: $ git update-ref HEAD HEAD^ Or if you’re not in the branch from which you cant to remove the last commit: $ git update-ref refs/heads/branch-name branch-name^ You could also pass a sha1 if you want: $ git update-ref refs/heads/branch-name a12d48e2 … Read more
A post-receive hook gets its arguments from stdin, in the form: <oldrev> <newrev> <refname> Since these arguments are coming from stdin, not from a command line argument, you need to use read instead of $1 $2 $3. The post-receive hook can receive multiple branches at once (for example if someone does a git push –all), … Read more
Another difference between a bare and non-bare repository is that a bare repository does not have a default remote origin repository: ~/Projects$ git clone –bare test bare Initialized empty Git repository in /home/derek/Projects/bare/ ~/Projects$ cd bare ~/Projects/bare$ git branch -a * master ~/Projects/bare$ cd .. ~/Projects$ git clone test non-bare Initialized empty Git repository in … Read more
In short: replace the contents of repo with the contents of repo/.git, then tell the repository that it is now a bare repository. To do this, execute the following commands: cd repo mv .git ../repo.git # renaming just for clarity cd .. rm -fr repo cd repo.git git config –bool core.bare true Note that this … Read more