-
Notifications
You must be signed in to change notification settings - Fork 6.2k
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 commitizen to repo to make it easy to follow conventional-commits #6844
Conversation
This makes it so that you only need to run 'git commit' in order to get conventional-commit compliant commits.
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This is a re-open of #6659 so I'm just currently waiting on this getting approved. Now this PR just has one single commit. |
Lighthouse Results
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Thanks for your patience here and for iterating on this PR! |
The most critical workflow I want to ensure we don't change is the blog post release process. Has anyone tested that yet? edit: Marco said this would not affect him |
Alrighty, I believe we can merge this. If issues eventually rise, we can just revert and investigate :) |
Description
This makes it so that you only need to run 'git commit' in order to get conventional-commit compliant commits.
Validation
Related Issues
Check List
npm run format
to ensure the code follows the style guide.npm run test
to check if all tests are passing.npx turbo build
to check if the website builds without errors.