From 63c7d00e75585abbc4bdfa08aa3d1eb6bf20cb89 Mon Sep 17 00:00:00 2001 From: Behdad Esfahbod Date: Fri, 3 Apr 2026 00:13:53 -0600 Subject: [PATCH] [docs] Require single-issue commits in AGENTS.md Add an explicit commit-guidance rule to keep each commit focused on a single issue or concern, instead of combining unrelated fixes, renames, refactors, or behavior changes. Co-authored-by: OpenAI Codex --- AGENTS.md | 1 + 1 file changed, 1 insertion(+) diff --git a/AGENTS.md b/AGENTS.md index d92e3d5e4..9cdd52c40 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -94,6 +94,7 @@ For API work: - Before any commit, run the entire test suite with `meson test -C build`. - Exception: simple documentation-only or CI-only changes may be committed without running tests if they do not affect code, build logic, generated outputs, or test inputs. +- Keep each commit focused on a single issue or concern. Do not combine unrelated fixes, API renames, refactors, or behavior changes into one commit unless the user explicitly asks for that. - Never push to the remote repository. The user handles pushing. - Use descriptive commit messages with consistent bracketed subsystem prefixes such as `[subset]`, `[raster]`, `[util]`, or `[meson]`. - Wrap commit message bodies to about 70 columns.