A git hook that checks whether there is an issue number in the first line of your commit message

100%

A git hook that checks whether there is an issue number in the first line of your commit message

✓ Published0🌍 Public

Last edited Jun 19, 2019

Created on Jun 19, 2019

This example demonstrates a Git hook that enforces commit message conventions by checking the first line for an issue number. It shows a Python script using the `sys` module to read the commit message file path passed as an argument. The script opens the file in read-write mode, reads all lines, and examines the first line for a `#` character, which indicates an issue reference. If no issue number is found, the script prints an error message and exits with a non-zero status code, blocking the commit. The code relies on standard Python file I/O and the `sys.argv` list to access command-line arguments, without external visualization libraries.

AI-generated description

Similar vizzes

Loading thumbnail…

pre-commit hook for larger files

This example shows a Bash script that automatically detects files larger than 50 megabytes in a Git repository and adds them to the `.gitignore` file, unless they are already ignored. The script uses `git check-ignore` to verify whether each file is excluded, and `find` with `-print0` to handle file names containing spaces. It normalizes paths relative to the repository root before appending them to `.gitignore`, ensuring large files are not accidentally committed.

ZZoeLeBlanc

54% match

Loading thumbnail…

git-hook to prevent pushing php-errors

This example demonstrates a Git pre-push hook that automatically scans outgoing PHP commits for syntax errors and aborts the push if any are found. It shows a shell script that uses `git diff-tree` to identify changed files, filters for `.php` extensions, and pipes each file through `php -l` (the PHP linter) to validate syntax. The hook receives pushed refs via standard input and acts on the SHA ranges, storing results in the local ref variables. It relies on standard Unix tools like `grep` and `xargs` to orchestrate the per-file linting process.

HHoffmannP

54% match

Loading thumbnail…

[転載] gitにおけるコミットログ/メッセージ例文集100

This example shows a curated collection of 100 real-world Git commit messages in English, organized by common actions like adding features, fixing bugs, and refactoring code. It demonstrates how to use imperative verb forms and concise phrasing for clear version control history. The data comes from GitHub repositories including Swift, Atom, Electron, Rails, and TensorFlow, filtered from over 25,000 commits. The display uses plain text formatting within a markdown file, with section headers and bullet lists to group similar message patterns.

RRytNszn

52% match

Loading thumbnail…

Reminder for signing Git commits

This example visualizes a reminder system for signing Git commits, showing how a terminal-based script triggers a notification workflow. It uses the `tty.bash` script, which exports `GPG_TTY` to ensure GPG signing works correctly in interactive terminal sessions. The visualization captures the command-line environment where the script runs, highlighting the integration between shell configuration and Git’s commit-signing process. The rendering relies on standard Bash syntax and environment variable handling, with no external data sources or graphical libraries—it presents a purely code-driven scenario focused on developer tooling.

CCliffordAnderson

51% match

Loading thumbnail…

Standard pre commit and isort, flake8 settings

This example shows a standardized Python project configuration that enforces consistent code style through pre-commit hooks, isort, and flake8. The `.pre-commit-config.yaml` file orchestrates multiple git hooks, including Black for formatting, isort for import sorting, flake8 for linting, and mypy for type checking, all triggered on commit and push stages. The `.flake8` and `.isort.cfg` files specify matching rules like an 88-character line limit, while the Makefile defines an `rtestthat` local hook that runs R tests via `source("tests/testthat.R")`.

Aandyreagan

49% match

Loading thumbnail…

Gist 9979190ea462c76d13e80def7b5aa3d8

This example demonstrates a Node.js script that checks whether the current Git branch is "master" before allowing a publish operation. It shows how to enforce a branch-based gate using the `execa` library to run `git symbolic-ref --short HEAD` and compare the output. The visualization highlights the workflow of validating Git state programmatically, with the script exiting with an error if the branch condition is not met. The code uses `execa.stdout` for asynchronous command execution, mirroring patterns from the `np` package. The rendering approach is text-based, relying on console output for success or failure.

HHypercubed

49% match

Loading thumbnail…

Gist 614541

This example visualizes a command-line prompt configuration that dynamically displays the current Git branch and working-directory status in color. It shows how the prompt turns red when uncommitted changes exist and green when the working directory is clean. The shell script uses `parse_git_branch` with `sed` and `awk`-style piping to extract branch names, while `check_git_changes` relies on `git status` and `tput setaf` to set terminal colors. The PS1 variable composes the final prompt, embedding the branch name and status indicator between the directory path and a colon. It relies on standard Bash and Git command-line tools, not a visualization library.

DDylanFM

47% match

Loading thumbnail…

powershell wtf

This example illustrates a PowerShell script that extracts a changeset ID from a Git commit message using two different approaches. It first demonstrates a successful method using a `Where-Object` pipeline with a regular expression, followed by a direct `-Match` operator, both printing the captured group to the console. The script then shows a commented-out version where the `-Match` operator fails, producing a "Cannot index into a null array" error, highlighting the difference in handling matched results. The code relies on PowerShell's built-in regex matching and `Write-Host`, drawing data from `git log`.

RRestuta

46% match