Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 184.108.40.206 → 220.127.116.11 no changes
- 1.8.3 05/24/13
- 18.104.22.168 → 22.214.171.124 no changes
- 126.96.36.199 08/24/11
- 188.8.131.52 → 1.7.6 no changes
- 1.7.5 04/24/11
- 184.108.40.206 → 220.127.116.11 no changes
- 1.7.4 01/31/11
- 18.104.22.168 → 22.214.171.124 no changes
- 1.6.3 05/07/09
- 126.96.36.199 → 188.8.131.52 no changes
- 184.108.40.206 01/25/09
- 220.127.116.11 → 1.6.1 no changes
- 1.6.0 08/17/08
- 18.104.22.168 → 22.214.171.124 no changes
- 1.5.6 06/18/08
- 126.96.36.199 → 188.8.131.52 no changes
- 1.5.4 02/02/08
- 184.108.40.206 → 220.127.116.11 no changes
- 1.5.3 09/02/07
git-shell(1) Manual Page
git-shell - Restricted login shell for Git-only SSH access
chsh -s $(command -v git-shell) <user> git clone <user>@localhost:/path/to/repo.git ssh <user>@localhost
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 named git-shell-commands in the user's home directory.
git shell accepts the following commands after the -c option:
- 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(1).
If a ~/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 directory.
By default, the commands above can be executed only with the -c option; the shell is not interactive.
If a ~/git-shell-commands directory is present, git shell can also be run interactively (with no arguments). If a help 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 the connection.
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.
If a 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
ssh(1), git-daemon(1), contrib/git-shell-commands/README
Part of the git(1) suite