Skip to content

fix(ci): lint only PR title since repo is squash-merge only#950

Merged
cv merged 1 commit intomainfrom
cv/commitlint-pr-title-only
Mar 26, 2026
Merged

fix(ci): lint only PR title since repo is squash-merge only#950
cv merged 1 commit intomainfrom
cv/commitlint-pr-title-only

Conversation

@cv
Copy link
Copy Markdown
Contributor

@cv cv commented Mar 26, 2026

Summary

The repo uses squash-merge exclusively. Individual commit messages are
discarded at merge time — only the PR title becomes the commit on main
and drives changelog generation.

This PR removes the per-commit lint step from the commit-lint workflow
and keeps only the PR title check. Also drops fetch-depth: 0 (no
longer needed) and fixes a pre-existing markdownlint MD032 in README.md.

Context: PR #913 has a commit created via GitHub's web-UI
"Apply suggestion" feature which doesn't follow conventional commit
format. Rather than special-casing those, this aligns the CI check with
what actually matters for the squash-merge workflow.

Test plan

Summary by CodeRabbit

  • Chores
    • Updated commit linting workflow to validate pull request titles.
    • Minor documentation formatting updates.

Individual commit messages are discarded at squash-merge — only the
PR title lands in main and drives changelog generation. Remove the
per-commit lint step and keep the PR title check.

Also drop fetch-depth: 0 (no longer walking commit history) and fix
a pre-existing markdownlint MD032 in README.md.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai bot commented Mar 26, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 1dae80c2-05e7-40d4-9bea-a922c31d76b4

📥 Commits

Reviewing files that changed from the base of the PR and between 0acb2e4 and a7c999e.

📒 Files selected for processing (2)
  • .github/workflows/commit-lint.yaml
  • README.md

📝 Walkthrough

Walkthrough

The commit-lint workflow was simplified to lint only PR titles instead of range-based commit messages, with the git fetch-depth configuration removed. A blank line was added to the README's macOS checklist for formatting.

Changes

Cohort / File(s) Summary
GitHub Workflow Simplification
.github/workflows/commit-lint.yaml
Removed commit message linting between base and head SHAs; now lints only PR title. Removed fetch-depth: 0 git configuration.
Documentation Formatting
README.md
Added blank line before "missing developer tools…" bullet in macOS first-run checklist section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 The workflow now runs lean and light,
PR titles alone shine bright,
A blank line hops into place—
Simple beauty, perfect grace!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately reflects the main change: removing per-commit linting from the CI workflow and keeping only the PR title check, which aligns with the repo's squash-merge-only policy.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch cv/commitlint-pr-title-only

Comment @coderabbitai help to get the list of available commands and usage tips.

@cv cv requested a review from kjw3 March 26, 2026 02:07
@cv cv merged commit e5e5d5a into main Mar 26, 2026
12 checks passed
@cv cv deleted the cv/commitlint-pr-title-only branch March 26, 2026 02:14
lakamsani pushed a commit to lakamsani/NemoClaw that referenced this pull request Apr 4, 2026
Individual commit messages are discarded at squash-merge — only the
PR title lands in main and drives changelog generation. Remove the
per-commit lint step and keep the PR title check.

Also drop fetch-depth: 0 (no longer walking commit history) and fix
a pre-existing markdownlint MD032 in README.md.
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