fix(ci): lint only PR title since repo is squash-merge only#950
Merged
Conversation
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.
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThe 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
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
brandonpelfrey
approved these changes
Mar 26, 2026
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The repo uses squash-merge exclusively. Individual commit messages are
discarded at merge time — only the PR title becomes the commit on
mainand drives changelog generation.
This PR removes the per-commit lint step from the
commit-lintworkflowand keeps only the PR title check. Also drops
fetch-depth: 0(nolonger 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
commit-lintCI job passes on this PRcommit-lintjob passes after this mergesSummary by CodeRabbit