Skip to content

ci: Validate pull request commit messages#32

Merged
arighi merged 1 commit into
NVIDIA:mainfrom
nirmoy:codex/commit-message-ci
Jul 7, 2026
Merged

ci: Validate pull request commit messages#32
arighi merged 1 commit into
NVIDIA:mainfrom
nirmoy:codex/commit-message-ci

Conversation

@nirmoy

@nirmoy nirmoy commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • enforce subsystem: Description subjects and 72-column prose for non-merge PR commits
  • preserve recognized Git trailers and report all violations as workflow annotations
  • document the policy and add dependency-free shell regression tests

Why

PR #29 needed several commit-message rewrites, and its final approved message still contained a 74-column prose line. A deterministic check makes the policy consistent and keeps review focused on the change itself.

Validation

  • .github/scripts/test-check-commit-messages.sh
  • bash -n .github/scripts/check-commit-messages.sh .github/scripts/test-check-commit-messages.sh
  • cargo +stable fmt --all -- --check
  • cargo +stable test --all-targets --locked (399 tests)
  • local YAML syntax parse
  • replayed PR lore: URL-encode message-id path segments #29 and confirmed its 74-column line is rejected

Check every non-merge pull request commit for the repository's subject
format and 72-column prose limit. Report violations as workflow
annotations while preserving recognized Git trailers.

Document the policy and cover valid, invalid, boundary, trailer, and
merge cases with a dependency-free shell test.

Signed-off-by: Nirmoy Das <nirmoyd@nvidia.com>
@nirmoy nirmoy marked this pull request as ready for review July 7, 2026 11:00
@nirmoy nirmoy requested a review from arighi July 7, 2026 11:00

@arighi arighi left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@arighi arighi merged commit 4d95e99 into NVIDIA:main Jul 7, 2026
2 checks passed
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.

2 participants