Skip to content

ci: gate PRs on commit-message hygiene - #136

Merged
tecfu merged 1 commit into
masterfrom
chore/commit-hygiene-gate
Oct 12, 2026
Merged

tecfu merged 1 commit into
masterfrom
chore/commit-hygiene-gate

Conversation

@tecfu

@tecfu tecfu commented Oct 12, 2026

Copy link
Copy Markdown
Owner

Follow-up to the discussion about commit descriptions surviving merges: master keeps real merge commits, but branches land with CI-debug churn (PR #127 alone carries ~25 commits whose subject is some variant of "save golden output").

Changes

  • ci.yml: new commit-hygiene job (pull_request events only) that fails a PR when it
    1. repeats a commit subject already used on the branch (sort | uniq -d), or
    2. uses a churn-pattern subject (save (actual|exact).*output, .*golden.*output, normalize .*output, retrigger, bare WIP/fix/lint).
  • CONTRIBUTING.md: the workflow the gate enforces — git commit --fixup + git rebase -i --autosquash before review, one logical change per commit, and the debugging narrative belongs in the PR conversation, not the log.

Validation

The check was reproduced against merged history: applied to PR #127 as it landed, it flags 30 of its 44 commits; PRs #133/#134 pass with zero. YAML parses; golden-file and unit suites are green on the branch base (8d3816e).

Sincerely qwen3.8-flash-next

Adds a commit-hygiene job that fails a PR whose commits duplicate a subject already on the branch or use CI-churn messages (save actual output, update golden output, retrigger CI, WIP), plus CONTRIBUTING.md spelling out the rebase --autosquash workflow the gate enforces.

Validated against merged history: PR #127 flags 30 of 44 commits (the golden-output saga); PRs #133/#134 pass clean.
@tecfu
tecfu merged commit 7cc410a into master Oct 12, 2026
5 checks passed
@tecfu
tecfu deleted the chore/commit-hygiene-gate branch October 12, 2026 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant