# git hook Published articles for git hook. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Using Git Pre-Commit Hooks DevFeed: [Using Git Pre-Commit Hooks]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2025-10-20T15:00:00Z Content type: tutorial Language: en Sources: [Scott's Weblog]() Topics: [Git](), [Markdown](), [Bash](), [Script]() Tags: [aws](), [bash](), [cilium](), [cli](), [cloud](), [cni](), [code](), [containers](), [cri-o](), [devops](), [docker](), [git](), [git-commit](), [git-hook](), [go](), [hooks](), [iac](), [k8s](), [kubernetes](), [lint](), [linux](), [markdown](), [networking](), [oci](), [script](), [security](), [tests]() ### AI overview This tutorial explains Git pre-commit hooks and demonstrates using one to run Markdownlint on staged Markdown files before a commit. It notes that a non-zero hook exit status aborts the commit and presents a Bash implementation based on the author's site. ### Source excerpt A while ago I wrote an article about linting Markdown files with markdownlint. In that article, I presented the use case of linting the Markdown source files for this site. While manually running linting checks is fine--there are times and situations when this is appropriate and necessary--this is the sort of task that is ideally suited for a Git pre-commit hook. In this post, I'll discuss Git pre-commit hooks in the context of using them to run linting checks. Before moving on, a disclaimer: I am not an expert on Git hooks. This post shares my limited experience and provides an example based on what I use for this site. I have no doubt that my current implementation will improve over time as my knowledge and experience grow. What is a Git Hook? As this page explains, a hook is a program "you can place in a hooks directory to trigger actions at certain points in git's execution." Generally, a hook is a script of some sort. Git supports different hooks that get invoked in response to specific actions in Git; in this particular instance, I'm focusing on the pre-commit hook. This hook gets invoked by git-commit (i.e., the user running a git commit command) and allows users to perform a series of checks or tests before actually making a commit. If the pre-commit script exits with a non-zero status, then Git aborts the commit. Using a Pre-Commit Hook to Lint Markdown For my use case, I wanted to run Markdownlint to lint the Markdown files (as described in the previous article on linting Markdown) before the commit. To do that, I came up with the following script: #!/usr/bin/env bash MDLINT="/usr/local/bin/markdownlint" for file in $(git diff --cached --name-only --diff-filter=ACM | grep "\.md"); do if ! $MDLINT "$file"; then echo "Lint check failed on file '$file'." echo "Run markdownlint to identify the errors and try again." exit 1 fi done To make this script active as a pre-commit hook, you must name it pre-commit, you must place it into Git's hook directory (which defa ## A component-based approach to managing team responsibility in Badoo and Bumble DevFeed: [A component-based approach to managing team responsibility in Badoo and Bumble]() Original publisher: [Read original article]() Author: Unclead (Badoo) Published: 2021-06-09T15:08:15Z Content type: article Language: ru Sources: [Badoo EN](), [Badoo RU]() Topics: [PHP](), [phpstorm](), [Git]() Tags: [badoo](), [bus-factor](), [git-hook](), [php](), [phpstorm](), [tag-622612a5798e](), [tag-a3f08f91b7c9](), [tag-b3a84f87fd83](), [tag-c51cc4bf76e5](), [team]() ### AI overview The article describes how Badoo and Bumble addressed the challenge of identifying teams and maintainers responsible for parts of a growing PHP codebase. It explains the limitations of DocBlock tags, PhpStorm templates, and a Git hook, and introduces a component-based approach intended to centralize responsibility information and let other systems consume updates automatically. ### Source excerpt Меня зовут Евгений Тупиков, я ведущий PHP-разработчик в Badoo и Bumble. У нас в команде более 200 бэкенд-разработчиков, которые работают над сотнями модулей и отдельных сервисов в наших приложениях. Но поначалу всё было не так масштабно. В 2006 году это был один проект, над которым работала небольшая команда. Каждый разработчик хорошо понимал, как всё устроено: легко ориентировался в коде, знал, какие есть сервисы и как они взаимодействуют между собой. Однако по мере роста проекта всё больше времени занимал поиск "хранителей знаний" -- тех, кто отвечает за ту или иную функциональность и к кому можно обратиться с вопросом или предложением. В этой статье я расскажу, как мы решили проблему разделения зон ответственности и сделали процесс актуализации информации быстрым и удобным с помощью компонентного подхода. Читать далее ## Detect when node\_modules are out of sync DevFeed: [Detect when node\_modules are out of sync]() Original publisher: [Read original article]() Published: 2020-09-01T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Node.js](), [Git](), [Script](), [Visual Studio Code](), [webstorm]() Tags: [git](), [git-hook](), [hooks](), [node](), [node-js](), [tooling](), [vscode](), [webstorm]() ### AI overview A tutorial on detecting when node_modules are out of sync after switching Git branches or commits. It explains a Node.js script that checks changed files for package.json and describes installing the script as a Git checkout hook. ### Source excerpt Lorem ipsum dolor sit amet ## Merge Git Authors DevFeed: [Merge Git Authors]() Original publisher: [Read original article]() Author: Artur Dryomov Published: 2019-03-19T00:00:00Z Content type: tutorial Language: en Sources: [Artur Dryomov]() Topics: [Git](), [git hook](), [bitbucket]() Tags: [bitbucket](), [consistency](), [email](), [git](), [git-hook](), [github](), [merge]() ### AI overview This article explains how to identify and consolidate inconsistent Git author names and email addresses so repository history accurately reflects contributor identities. It discusses Git commands, display limitations, tool support, and preventive checks using Bitbucket plugins or pre-commit hooks. ### Source excerpt Stats! Stats are awesome. You can collect them, you can analyze and visualize them, you can boil, grill and fry them... Wait, that's not food, right? git shortlog Let's say we have a Git repository. We want to count commits per author. There is a Git command for that! $ git shortlog --summary --numbered 2 Bender Rodriguez 2 Philip J. Fry 1 Bending Unit 22 1 Turanga Leela There are actually three authors but since names are non-consistent Git makes it look like there are four. It gets worse with emails. ## git pre-commit hook for code beautification DevFeed: [git pre-commit hook for code beautification]() Original publisher: [Read original article]() Author: Ramon Published: 2016-01-30T20:22:19Z Content type: tutorial Language: en Sources: [Ramon Fried]() Topics: [Git](), [Linux](), [Script](), [Kernel](), [Command-line interface]() Tags: [artistic-style](), [astyle](), [code-beautification](), [coding-style](), [command-line](), [git](), [git-commit](), [git-hook](), [how-to](), [improvements](), [kernel](), [linux](), [linux-kernel](), [script](), [uncategorized](), [workflow]() ### AI overview A tutorial on using a Git pre-commit hook to automate code beautification. The hook runs astyle on files included in a commit, helping apply formatting rules such as spacing and indentation; the article also discusses Linux user-space and kernel coding styles and the checkpatch.pl script. ### Source excerpt Hi. In this post I will share a git pre-commit hook I created for aiding with code beautification. In Linux, I work in two different coding styles: User space and Kernel. The Linux kernel has a very specific coding style and every commit to kernel must adhere to that style. The Linux kernel provides a [...]