Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
core: multiple scopes in commit message
See original GitHub issueHi,
I have a project where the commitlint is used to enforce the commit message using the angular & lerna-scopes config. This works fine for most messages but it errors for multiple scopes in a message: Example: fix(core,context): fixed some situation.
Is there a configuration to support this or should this be a feature request?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:12
- Comments:12 (4 by maintainers)
Top Results From Across the Web
conventional commits - Commitlint - Allow '/' in scope-enum
According to source code, Commitlint use / for multiple scopes. It means, you can commit like fix(core/account): fix border but you can't ...
Read more >Conventional Commits
The Conventional Commits specification is a lightweight convention on top of commit messages. It provides an easy set of rules for creating an...
Read more >commitlint - Lint commit messages
commitlint helps your team adhere to a commit convention. By supporting npm-installed configurations it makes sharing of commit conventions easy.
Read more >Conventional Commits - Uno Platform
Uno uses the Conventional Commits format for all changes to the source ... allow you to edit the commit message. if you have...
Read more >Implementing an Implicit Transaction using Transaction Scope
If the ambient transaction was created by a root scope, only when the root scope is disposed of, does Commit get called on...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for the quick reply @marionebl 😃
For a lerna project with the following packages:
Current Behaviour
Commit Message:
feat(pkg1, pkg2): add some new featurecommitlint Error:scope must be one of [pkg1, pkg2, pkg3, pkg4]Expected Behaviour
As long as all the scopes are valid and comma separated, the commit message should pass commitlint.
Reason: Some features/fixes may at times require multiple packages to be changed and this approach allows all affected scopes to be listed.
Could this be closed as https://github.com/conventional-changelog/commitlint/pull/901 was merged?