GitHub Enterprise Server の pre-receive フックの例は、github/platform-samples
リポジトリで見ることができます。
pre-receiveフックスクリプトの作成
A pre-receive hook script executes in a pre-receive hook environment on GitHub Enterprise Serverインスタンス. When you create a pre-receive hook script, consider the available input, output, exit status, and environment variables.
Input (stdin
)
After a push occurs and before any refs are updated for the remote repository, the git-receive-pack
process on GitHub Enterprise Serverインスタンス invokes the pre-receive hook script. Standard input for the script, stdin
, is a string containing a line for each ref to update. Each line contains the old object name for the ref, the new object name for the ref, and the full name of the ref.
<old-value> SP <new-value> SP <ref-name> LF
This string represents the following arguments.
引数 | 説明 |
---|---|
<old-value> | Old object name stored in the ref. When you create a new ref, the value is 40 zeroes. |
<new-value> | New object name to be stored in the ref. When you delete a ref, the value is 40 zeroes. |
<ref-name> | The full name of the ref. |
For more information about git-receive-pack
, see "git-receive-pack" in the Git documentation. For more information about refs, see "Git References" in Pro Git.
Output (stdout
)
The standard output for the script, stdout
, is passed back to the client. Any echo
statements will be visible to the user on the command line or in the user interface.
終了ステータス
The exit status of a pre-receive script determines if the push will be accepted.
Exit-status value | アクション |
---|---|
0 | プッシュは受け付けられます。 |
0以外 | プッシュは拒否されます。 |
環境変数
In addition to the standard input for your pre-receive hook script, stdin
, GitHub Enterprise Server makes the following variables available in the Bash environment for your script's execution. For more information about stdin
for your pre-receive hook script, see "Input (stdin
)."
Different environment variables are available to your pre-receive hook script depending on what triggers the script to run.
- Always available
- Available for pushes from the web interface or API
- Available for pull request merges
- Available for pushes using SSH authentication
Always available
The following variables are always available in the pre-receive hook environment.
変数 | 説明 | 値の例 |
---|---|---|
$GIT_DIR | Path to the remote repository on the instance | /data/user/repositories/a/ab/ a1/b2/34/100001234/1234.git |
$GIT_PUSH_OPTION_COUNT | The number of push options that were sent by the client with --push-option . For more information, see "git-push" in the Git documentation. | 1 |
$GIT_PUSH_OPTION_N | ここで N は 0 から始まる整数で、この変数にはクライアントから送信されたプッシュオプションの文字列が含まれます。 The first option that was sent is stored in GIT_PUSH_OPTION_0 , the second option that was sent is stored in GIT_PUSH_OPTION_1 , and so on. プッシュオプションに関する詳しい情� �については、Gitのドキュメンテーションのgit-pushを参照してく� さい。 | abcd |
$GIT_USER_AGENT | User-agent string sent by the Git client that pushed the changes | git/2.0.0 |
$GITHUB_REPO_NAME | Name of the repository being updated in NAME/OWNER format | octo-org/hello-enterprise |
$GITHUB_REPO_PUBLIC | Boolean representing whether the repository being updated is public |
|
$GITHUB_USER_IP | IP address of client that initiated the push | 192.0.2.1 |
$GITHUB_USER_LOGIN | Username for account that initiated the push | octocat |
Available for pushes from the web interface or API
The $GITHUB_VIA
variable is available in the pre-receive hook environment when the ref update that triggers the hook occurs via either the web interface or the API for GitHub Enterprise Server. The value describes the action that updated the ref.
値 | アクション | 詳細情� � |
---|---|---|
auto-merge deployment api | Automatic merge of the base branch via a deployment created with the API | "Create a deployment" in the REST API documentation |
blob#save | Change to a file's contents in the web interface | "Editing files" |
branch merge api | Merge of a branch via the API | "Merge a branch" in the REST API documentation |
branches page delete button | Deletion of a branch in the web interface | 「リポジトリ内でのブランチの作成と削除」 |
git refs create api | Creation of a ref via the API | "Git database" in the REST API documentation |
git refs delete api | Deletion of a ref via the API | "Git database" in the REST API documentation |
git refs update api | Update of a ref via the API | "Git database" in the REST API documentation |
git repo contents api | Change to a file's contents via the API | "Create or update file contents" in the REST API documentation |
|
merge
| Merge of a pull request using auto-merge | "Automatically merging a pull request" |
|
merge base into head| Update of the topic branch from the base branch when the base branch requires strict status checks (via Update branch in a pull request, for example) | "About protected branches" | |
pull request branch delete button| Deletion of a topic branch from a pull request in the web interface | "Deleting and restoring branches in a pull request" | |
pull request branch undo button| Restoration of a topic branch from a pull request in the web interface | "Deleting and restoring branches in a pull request" | |
pull request merge api| Merge of a pull request via the API | "Pulls" in the REST API documentation | |
pull request merge button| Merge of a pull request in the web interface | "Merging a pull request" | |
pull request revert button| Revert of a pull request | "Reverting a pull request" | |
releases delete button| Deletion of a release | "Managing releases in a repository" | |
stafftools branch restore| Restoration of a branch from the site admin dashboard | "Site admin dashboard" | |
tag create api| Creation of a tag via the API | "Git database" in the REST API documentation | |
slumlord (#SHA)| Commit via Subversion | "Support for Subversion clients" | |
web branch create| Creation of a branch via the web interface | "Creating and deleting branches within your repository" |
Available for pull request merges
The following variables are available in the pre-receive hook environment when the push that triggers the hook is a push due to the merge of a pull request.
変数 | 説明 | 値の例 |
---|---|---|
$GITHUB_PULL_REQUEST_AUTHOR_LOGIN | Username of account that authored the pull request | octocat |
$GITHUB_PULL_REQUEST_HEAD | The name of the pull request's topic branch, in the format USERNAME:BRANCH | |
$GITHUB_PULL_REQUEST_BASE | The name of the pull request's base branch, in the format USERNAME:BRANCH | octocat:main |
Available for pushes using SSH authentication
変数 | 説明 | 値の例 |
---|---|---|
$GITHUB_PUBLIC_KEY_FINGERPRINT | The public key fingerprint for the user who pushed the changes | a1:b2:c3:d4:e5:f6:g7:h8:i9:j0:k1:l2:m3:n4:o5:p6 |
権限の設定と GitHub Enterprise Server への pre-receive フックのプッシュ
A pre-receive hook script is contained in a repository on GitHub Enterprise Serverインスタンス. サイト管理者はリポジトリの権限を考慮し、適切なユーザ� けがアクセスできるようにしなければなりません。
フックは単一のリポジトリに集約することをおすすめします。 集約されたフックのリポジトリがパブリックになっている� �合、README.md
をポリシーの強制の説明に利用できます。 また、コントリビューションをプルリクエスト経由で受け付けることもできます。 しかし、pre-receiveフックはデフォルトブランチからのみ追� できます。 テストのワークフロー用には、設定を持つリポジトリのフォークを使うべきです。
-
Mac ユーザは、スクリプトに実行権限を持たせてく� さい。
$ sudo chmod +x SCRIPT_FILE.sh
Windows ユーザは、スクリプトに実行権限を持たせてく� さい。
git update-index --chmod=+x SCRIPT_FILE.sh
-
Commit and push to the designated repository for pre-receive hooks on GitHub Enterprise Serverインスタンス.
$ git commit -m "YOUR COMMIT MESSAGE" $ git push
-
Create the pre-receive hook on the GitHub Enterprise Server instance.
ローカルでのpre-receiveスクリプトのテスト
You can test a pre-receive hook script locally before you create or update it on GitHub Enterprise Serverインスタンス. その方法の 1 つは、pre-receive フックを実行できるリモートリポジトリとして働くローカルの Docker 環境を作成することです。
-
ローカルにDockerがインストールされていることを確認してく� さい。
-
以下を含む
Dockerfile.dev
というファイルを作成してく� さい。FROM gliderlabs/alpine:3.3 RUN \ apk add --no-cache git openssh bash && \ ssh-keygen -A && \ sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && \ adduser git -D -G root -h /home/git -s /bin/bash && \ passwd -d git && \ su git -c "mkdir /home/git/.ssh && \ ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P '' && \ mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && \ mkdir /home/git/test.git && \ git --bare init /home/git/test.git" VOLUME ["/home/git/.ssh", "/home/git/test.git/hooks"] WORKDIR /home/git CMD ["/usr/sbin/sshd", "-D"]
-
always_reject.sh
というテストのpre-receiveスクリプトを作成してく� さい。 このスクリプト例では、全てのプッシュを拒否します。これは、リポジトリをロックする� �合に役立ちます。#!/usr/bin/env bash echo "error: rejecting all pushes" exit 1
-
always_reject.sh
スクリプトが実行権限を持つことを確認してく� さい。$ chmod +x always_reject.sh
-
Dockerfile.dev
を含むディレクトリからイメージをビルドしてく� さい。$ docker build -f Dockerfile.dev -t pre-receive.dev . > Sending build context to Docker daemon 3.584 kB > Step 1 : FROM gliderlabs/alpine:3.3 > ---> 8944964f99f4 > Step 2 : RUN apk add --no-cache git openssh bash && ssh-keygen -A && sed -i "s/#AuthorizedKeysFile/AuthorizedKeysFile/g" /etc/ssh/sshd_config && adduser git -D -G root -h /home/git -s /bin/bash && passwd -d git && su git -c "mkdir /home/git/.ssh && ssh-keygen -t ed25519 -f /home/git/.ssh/id_ed25519 -P ' && mv /home/git/.ssh/id_ed25519.pub /home/git/.ssh/authorized_keys && mkdir /home/git/test.git && git --bare init /home/git/test.git" > ---> Running in e9d79ab3b92c > fetch http://alpine.gliderlabs.com/alpine/v3.3/main/x86_64/APKINDEX.tar.gz > fetch http://alpine.gliderlabs.com/alpine/v3.3/community/x86_64/APKINDEX.tar.gz ....truncated output.... > OK: 34 MiB in 26 packages > ssh-keygen: generating new host keys: RSA DSA ECDSA ED25519 > Password for git changed by root > Generating public/private ed25519 key pair. > Your identification has been saved in /home/git/.ssh/id_ed25519. > Your public key has been saved in /home/git/.ssh/id_ed25519.pub. ....出力を省略.... > Initialized empty Git repository in /home/git/test.git/ > Successfully built dd8610c24f82
-
生成された SSH キーを含むデータコンテナを実行してく� さい。
$ docker run --name data pre-receive.dev /bin/true
-
テスト pre-receive フックの
always_reject.sh
をデータコンテナにコピーしてく� さい:$ docker cp always_reject.sh data:/home/git/test.git/hooks/pre-receive
-
sshd
を実行しフックを動作させるアプリケーションコンテナを実行してく� さい。 返されたコンテナ ID をメモしておいてく� さい:$ docker run -d -p 52311:22 --volumes-from data pre-receive.dev > 7f888bc700b8d23405dbcaf039e6c71d486793cad7d8ae4dd184f4a47000bc58
-
生成された SSH キーをデータコンテナからローカルマシンにコピーしてく� さい:
$ docker cp data:/home/git/.ssh/id_ed25519 .
-
テストリポジトリのリモートを修正して、Docker コンテナ内の
test.git
リポジトリにプッシュしてく� さい。 この例ではgit@github.com:octocat/Hello-World.git
を使用していますが、どのリポジトリを使用しても構いません。 この例ではローカルマシン (127.0.0.1) がポート 52311 をバインドしているものとしていますが、docker がリモートマシンで動作しているなら異なる IP アドレスを使うことができます。$ git clone git@github.com:octocat/Hello-World.git $ cd Hello-World $ git remote add test git@127.0.0.1:test.git $ GIT_SSH_COMMAND="ssh -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no -p 52311 -i ../id_ed25519" git push -u test main > Warning: Permanently added '[192.168.99.100]:52311' (ECDSA) to the list of known hosts. > Counting objects: 7, done. > Delta compression using up to 4 threads. > Compressing objects: 100% (3/3), done. > Writing objects: 100% (7/7), 700 bytes | 0 bytes/s, done. > Total 7 (delta 0), reused 7 (delta 0) > remote: error: rejecting all pushes > To git@192.168.99.100:test.git > ! [remote rejected] main -> main (pre-receive hook declined) > error: failed to push some refs to 'git@192.168.99.100:test.git'
pre-receive フックの実行後にプッシュが拒否され、スクリプトからの出力がエコーされていることに注意してく� さい。
参考リンク
- Pro Git Webサイトの「Gitのカスタマイズ - Gitポリシーの実施例」