fix: treat null & undefined as no-scope markers#3
Merged
ridvanaltun merged 1 commit intoJul 26, 2026
Merged
Conversation
omit from error messages
TobiTenno
force-pushed
the
fix/null-scope-marker-after-commitlint-load
branch
from
July 4, 2026 00:31
ae59d80 to
e1754c0
Compare
Contributor
Author
|
@ridvanaltun i think this finishes fixing #2 |
Contributor
Author
|
@ridvanaltun could you please review and merge this? #2 is still an issue |
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
2 participants
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
@commitlint/loadmerges config withes-toolkit, which turns arraynullentries intoundefined[null]for optional/absent scopes then fail withscopes: "undefined"nullandundefinedas no-scope markers; omit them from error messagesTest plan
[undefined]allows missing scope (commitlint load behavior)ci: bump the default group across 1 directory with 10 updatespasses