feat: exclude merge commits from --range by default#30
Merged
Conversation
A passing exit code with no commits checked is a silent false positive in CI — the range spec may be misconfigured or the fetch too shallow. Use --allow-empty to restore exit 0 when an empty range is intentional. Signed-off-by: Nerijus Bendžiūnas <nerijus.bendziunas@gmail.com>
Merge commits almost always fail the subject check and are rarely meaningful to lint. --no-merges is now the default for range checks; use --include-merges (or include-merges in .commit-guard.toml) to opt in to checking them. Signed-off-by: Nerijus Bendžiūnas <nerijus.bendziunas@gmail.com>
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
1 participant
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.
Uh oh!
There was an error while loading. Please reload this page.