gitwtfhub

wtf is gitte-rs?

gennarobiondi/gitte-rs — explained in plain English

Analysis updated 2026-05-18

2RustAudience · developerComplexity · 2/5Setup · easy

TL;DR

A Rust command line tool that checks your git commit messages and branch names against the Conventional Commits and Conventional Branch naming rules.

Mindmap

mindmap
  root((gitte-rs))
    What it does
      Checks commits
      Checks branches
      Prints warnings
    Tech stack
      Rust
      Cargo
    Use cases
      Commit checks
      Branch checks
    Audience
      Developers
      Rust users

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Check that every commit message in a repo follows the Conventional Commits format before merging.

REASON 2

Validate that branch names follow a type/description naming scheme before pushing.

REASON 3

Run as a lightweight check without setting up a full linting suite.

What's in the stack?

RustCargo

How it stacks up

gennarobiondi/gitte-rs132ikl/game1lystore/pay-dcp
Stars222
LanguageRustRustRust
Last pushed2020-12-30
MaintenanceDormant
Setup difficultyeasymoderatemoderate
Complexity2/52/53/5
Audiencedevelopergeneraldeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · easy Time to first run · 5min

Wtf does this do

gitte-rs is a command line tool written in Rust that checks whether your git commits and branch names follow common naming conventions. It looks at every commit and every branch in a repository and prints a warning when something does not match the expected pattern. The tool follows two established specifications: Conventional Commits and Conventional Branch. When you run the command with no arguments, it checks the git repository in your current folder. You can also give it a path to another repository on your machine and it will check that one instead. For commits, it looks for a structure like type(scope): description, for example fix(login): correct password check. It flags problems such as mismatched parentheses in the scope, a missing colon or scope, a missing description, non ASCII characters in the scope, whitespace inside the scope, or invalid characters like parentheses or the at symbol. It also warns if it does not recognize the commit type, though the author notes this is not really an error since custom types are allowed by the specification. For branches, it expects a structure like type/description, for example feat/add-login-page. Main, master, and develop branches are exempt from needing a slash. It flags a missing slash, a missing type before the slash, an unrecognized branch type, a missing description after the slash, uppercase letters in the description, underscores instead of hyphens, leading or trailing hyphens, and consecutive hyphens. The project is the successor to an earlier tool called glitter by the same author. It is distributed as a Rust crate through crates.io, so anyone with Rust and Cargo installed can add it to their toolchain. The README does not describe any configuration options beyond passing an optional path argument, and it does not mention any integration with git hooks, continuous integration systems, or editors. It is a small, focused checker rather than a full commit management suite.

Yoink these prompts

Prompt 1
Write a git pre-commit hook that runs the gitte-rs CLI to check commit messages before allowing a commit.
Prompt 2
Explain what the gitte-rs warning 'No description found!' means for my commit message.
Prompt 3
Show me how to install and run gitte-rs on a Rust project to check my branch naming conventions.
Prompt 4
Help me fix a branch name so it passes gitte-rs's Conventional Branch checks.

Frequently asked questions

wtf is gitte-rs?

A Rust command line tool that checks your git commit messages and branch names against the Conventional Commits and Conventional Branch naming rules.

What language is gitte-rs written in?

Mainly Rust. The stack also includes Rust, Cargo.

How hard is gitte-rs to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is gitte-rs for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.