Summary - Custom hooks

Combine the custom hook flow to set up server-side policy.

Summary: Server-Side Hook Policies

Custom hooks let you add automatic rules to Git operations. `pre-receive` checks all reference updates in an incoming push, while `update` checks each reference separately. Both hooks run on the server and can reject operations that violate a policy.

#!/bin/bash
# Server-side validation script
echo "Checking policy"

Exercise Write a Combined Server Policy

Write an `update` hook script. Use Bash, read the reference name from the first argument, and reject updates to `refs/heads/main`. Print an approval message for other references. This example represents a branch-specific server policy.

Show example solution

#!/bin/bash
refname="$1"
if [[ "$refname" == "refs/heads/main" ]]; then
  echo "Politika: ana dal korumalı" >&2
  exit 1
fi
echo "Politika: güncellemeye izin verildi"

Test yourself

Which hook is suitable for checking all references in a push together?
- update
- pre-receive
- A local shell script
- git status
Show answer

pre-receive — `pre-receive` can inspect the update information together before the push request is accepted.

Complete the Hook Policy

if [[ "$refname" == "refs/heads/main" ]]; then
  echo "Güncelleme reddedildi"
  _____ 1
fi____

Show answer

if [[ "$refname" == "refs/heads/main" ]]; then
  echo "Güncelleme reddedildi"
  _____ 1
fiexit

Match the Server-Side Policy Components

Hook betiği

Performs automatic validation
pre-receive

Checks the push request as a whole
update

Checks references separately
Politika

Defines permitted operations

Next lesson: What is LFS?

We Are Enhancing Your Experience

Cookie Preferences

Strictly Necessary Cookies

Analytical Cookies