Skip to content

[codex] Standardize commit message validation#172

Draft
pistell wants to merge 1 commit into
marcus:mainfrom
pistell:chore/commit-message-normalizer
Draft

[codex] Standardize commit message validation#172
pistell wants to merge 1 commit into
marcus:mainfrom
pistell:chore/commit-message-normalizer

Conversation

@pistell
Copy link
Copy Markdown

@pistell pistell commented May 24, 2026

What changed

  • added scripts/commit-msg.sh to validate commit subjects locally and in CI
  • updated make install-hooks to install both pre-commit and commit-msg hooks
  • documented the commit message contract, allowed types, exceptions, examples, and recovery flow in README.md
  • added a CI job that validates commit messages for pushes and pull requests with full history available

Why

Nightshift had mixed commit subject styles and no enforcement. This standardizes future commit messages without rewriting history and keeps local hooks and CI aligned on the same rule set.

Impact

Contributors and Nightshift-generated changes now share one commit message contract. Merge commits, generated reverts, and release/version bump commits remain valid so existing workflows are not disrupted.

Validation

  • bash -n scripts/commit-msg.sh scripts/pre-commit.sh
  • scripts/commit-msg.sh against valid and invalid sample messages
  • scripts/commit-msg.sh --rev-range main..HEAD
  • make install-hooks
  • go test ./...

Automated by nightshift

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