-
Notifications
You must be signed in to change notification settings - Fork 934
core: multiple scopes in commit message #75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Currently Could you elaborate on the error messages you see and the behaviour you expect? |
Thanks for the quick reply @marionebl :) For a lerna project with the following packages:
Current BehaviourCommit Message: Expected BehaviourAs 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. |
This would require:
|
I like the sound of a plugin API for rules :) That way additional rules can be written by the community as needed. Are you currently working on the this by any chance? I looked into |
Have not worked on plugins yet. I'd mostly copycat the eslint way of things, removing most effort for tech. concept etc. If |
Linking possible plugin PR |
It's not maintained anymore, but isn't cz-lerna-changelog an implementation of what's been discussed in this thread? Could be a good place to start. |
@PaulRBerg sorry, what is not maintained anymore? |
cz-lerna-changelog. I was just saying that they seem to have implemented multiple scopes, despite the fact that there hasn't been much activity on their repo lately. |
Ah, thx for clarifying! |
Could this be closed as #901 was merged? |
Thanks @backflip for pointing this out! Closing this 🎉 |
Hi,
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?
The text was updated successfully, but these errors were encountered: