Git Hooks: Automation in the Development Workflow

Git Hooks are shell scripts in the .git/hooks/ directory of a repository. Git executes them during specific events. The most important:

pre-commit. Runs before every commit. Checks coding standards, syntax errors and formats code automatically. If the script fails, the commit is aborted.

commit-msg. Checks the commit message. Enforces naming conventions like "PROJ-123: description" for traceability.

pre-push. Runs before a push. Starts unit tests or linting — the push is aborted if tests fail.

post-merge. Runs after a merge. Automatically executes "composer install" or "drush updatedb" so the local environment stays up to date.

PHP CodeSniffer. In the pre-commit hook, PHPCS checks code against Drupal coding standards. Incorrectly formatted code is not committed.

PHPStan. Static analysis finds type errors and undefined variables before code is executed.

YAML validation. Drupal configurations are stored as YAML files. A hook checks syntax and prevents faulty configurations.

Automatic formatting. Tools like PHP-CS-Fixer format code automatically in the pre-commit hook. No manual cleanup needed.

Git Hooks are local and not automatically shared. Tools like Husky, GrumPHP or Captain Hook solve this: the hook configuration is versioned in the repository and automatically installed during "composer install". Every team member works with the same quality checks.

arocom sets up Git Hooks and CI/CD pipelines for Drupal projects. The Future Check evaluates your development process. Starting at EUR 2,500 plus VAT, credited toward the follow-up project.