Blog¶
Release announcements, and the reasoning behind decisions the reference pages only state. Rules tells you what a rule does and how to configure it; these posts cover why it exists and what changed along the way.
-
"No LLM bots in Co-authored-by": checking the rule before the squash merge
Some projects close any pull request that credits an LLM as a co-author. Here is how to check that rule on every pull request, including the co-author lines a squash merge copies into main.
Xianpeng Shen commit-checkaigithub-app
-
Your AI agent signs your commits. Does your project have a policy for that?
AI coding agents stamp their own trailers on your commits. Open source has answered that three ways; here is how to enforce whichever one your project chose, on every commit.
-
AI Attribution Governance: Enforcing AI Disclosure Policies at the CI Level
AI Attribution Governance: Enforcing AI Disclosure Policies at the CI Level¶ The open-source ecosystem is converging on a hard question: when a commit is written with AI assistance, how do we know — and how do we enforce the disclosure...
-
AI-native: JSON output and a Python API
AI-native: JSON output and a Python API¶ More and more commits are written — or at least drafted — by AI agents and automation. So Commit Check is also built for machines — not just humans reading terminal output. This post covers the...
-
From zero-config to org-wide policy
From zero-config to org-wide policy¶ Commit Check works the moment you install it, but its real strength shows up when you start shaping the policy to fit your team. This post covers everything from the default behavior to...
-
One policy file for your Git history
One policy file for your Git history¶ Most teams have a wiki page titled something like "How we write commit messages." It covers commit conventions, branch naming, sign-offs, and author email consistency — and then nobody reads...