-
Notifications
You must be signed in to change notification settings - Fork 1
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
[commit-name] Commit names do not satisfy requirements #17
Comments
Bad commit name by @claudiorodriguez and @web-flow: BREAKING CHANGE: upgrades canonical
|
Commit complies with mol-fe guidelines |
Re-opened: please use semantic commit names |
Bad commit name by @carpasse and @claudiorodriguez:
following same pattern as eslint-config-canonical
|
All commit names satisfy requirements |
Re-opened: please use semantic commit names |
Bad commit name by @carpasse: Everthing exported should be named. This change also discorages exports like:
Which prevent efficient treeshaking. As the compiler can't know what BREAKING CHANGE: any anonymous export will fail from now on. |
Not a bad commit message |
Re-opened: please use semantic commit names |
Bad commit name by @Greenkeeper[bot] and @claudiorodriguez: |
Bad commit name by @claudiorodriguez: |
Bad commit name by @claudiorodriguez: Moves the rules in canonical inside the package BREAKING CHANGE: removes ava rules |
Bad commit name by @claudiorodriguez: There were some react overrides in the base config, |
Bad commit name by Vadim Dalecky and @streamich: |
Please use semantic commit names
The text was updated successfully, but these errors were encountered: