Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.14.3 → 2.16.2 no changes
- 2.14.2 09/22/17
- 2.14.1 no changes
- 2.14.0 08/04/17
- 2.13.6 09/22/17
- 2.13.1 → 2.13.5 no changes
- 2.13.0 05/09/17
- 2.12.5 09/22/17
- 2.12.1 → 2.12.4 no changes
- 2.12.0 02/24/17
- 2.11.4 09/22/17
- 2.11.1 → 2.11.3 no changes
- 2.11.0 11/29/16
- 2.10.5 09/22/17
- 2.9.4 → 2.10.4 no changes
- 2.9.3 08/12/16
chsh -s $(command -v git-shell) <user> git clone <user>
This is a login shell for SSH accounts to provide restricted Git access.
It permits execution only of server-side Git commands implementing the
pull/push functionality, plus custom commands present in a subdirectory
git-shell-commands in the user’s home directory.
git shell accepts the following commands after the
- git receive-pack <argument>
- git upload-pack <argument>
- git upload-archive <argument>
Call the corresponding server-side command to support the client’s git push, git fetch, or git archive --remote request.
- cvs server
Imitate a CVS server. See git-cvsserver.
~/git-shell-commands directory is present, git shell will
also handle other, custom commands by running
git-shell-commands/<command> <arguments>" from the user’s home
By default, the commands above can be executed only with the
option; the shell is not interactive.
~/git-shell-commands directory is present, git shell
can also be run interactively (with no arguments). If a
command is present in the
git-shell-commands directory, it is
run to provide the user with an overview of allowed actions. Then a
"git> " prompt is presented at which one can enter any of the
commands from the
git-shell-commands directory, or
exit to close
Generally this mode is used as an administrative interface to allow users to list repositories they have access to, create, delete, or rename repositories, or change repository descriptions and permissions.
no-interactive-login command exists, then it is run and the
interactive shell is aborted.
To disable interactive logins, displaying a greeting instead:
$ chsh -s /usr/bin/git-shell $ mkdir $HOME/git-shell-commands $ cat >$HOME/git-shell-commands/no-interactive-login <<\EOF #!/bin/sh printf '%s\n' "Hi $USER! You've successfully authenticated, but I do not" printf '%s\n' "provide interactive shell access." exit 128 EOF $ chmod +x $HOME/git-shell-commands/no-interactive-login
To enable git-cvsserver access (which should generally have the
no-interactive-login example above as a prerequisite, as creating
the git-shell-commands directory allows interactive logins):
$ cat >$HOME/git-shell-commands/cvs <<\EOF if ! test $# = 1 && test "$1" = "server" then echo >&2 "git-cvsserver only handles \"server\"" exit 1 fi exec git cvsserver server EOF $ chmod +x $HOME/git-shell-commands/cvs
ssh(1), git-daemon, contrib/git-shell-commands/README
Part of the git suite