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
add info about 'npm run c' to CONTRIBUTING.md #147
Comments
so just for clarity, for a PR like #131, if I had run |
Or an even better example: https://github.com/Esri/arcgis-rest-js/pull/115/commits - where other people have pulled the branch and made their own commits. In that case we still want to squash and push to get the right message, right? |
i think that the fact that the changelog parser ignores the extra commits means that its less important to squash. either way though. |
* chore(CONTRIBUTING): add info about commitizen ISSUES CLOSED: #147 * /end bold * noah has eagle 👀
our changelog parser zeros in commit message formatting that is generated by the command
npm run c
to categorize chores, bug fixes, features and breaking changes.we need to advertise this to new contributors (and old grizzly bears like @tomwayson)
The text was updated successfully, but these errors were encountered: