Therefore the workflow is to first init a regular private repository, then use this command to create the public one, then add the appropriate remote branch (cg-branch-add origin ...) in your private repository and then push to the public repository.

Use cg-init(1) if you want to instead create a new GIT project.

The command will create the repository to reside in DIRECTORY (the directory must not exist before calling this command). By default, it will be world-readable, but writable only by you. If you want to make it possible for multiple users to push, create a group for them and use the -g parameter, which will make cg-admin-setuprepo(1) set up the permissions properly.

The repository will also be set up so that git-update-server-info will be automagically re-ran after each push, in short making it suitable for HTTP access.

Note that you might need to do other additional steps, like touching the git-daemon-export-ok file if you want to make the repository accessible by the git daemon (serving the git://... URIs).

-g GROUP

Name of the UNIX group covering the users authorized to push into the repository. If unspecified, only you (who ran this command) will have write (push) access.

-h, --help

Print usage summary.

--long-help

Print user manual. The same as found in cg-admin-setuprepo(1).

#!/bin/sh
exec git-update-server-info