-
Notifications
You must be signed in to change notification settings - Fork 20
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
chore: Add PR title validation #169
Conversation
d4ea868
to
b5b31b1
Compare
- name: PR Conventional Commit Validation | ||
uses: ytanikin/[email protected] | ||
with: | ||
task_types: '["fix","feat","refactor","spike","hotfix","revert","chore","docs","test","build"]' |
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.
Missing ci
and perf
?
I'm looking at this list: https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines
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.
We haven't included those in our guide in Notion, but we could. IIRC, we thought ci
didn't add much that build
doesn't already cover, but perf
could be an interesting one to add.
@bgins this feels like something we need to socialise so that the team are aware how to write their PR titles |
Yes absolutely! I'll give a quick presentation at engineering catchup tomorrow. |
thanks @bgins ! |
b5b31b1
to
4cc3ca4
Compare
Review Type Requested (choose one):
Summary
This pull request adds a PR title validation GitHub action. The action checks that PR titles use conventional commits from a custom list matching our task types.
The GitHub action also labels PRs based on the task type. The
custom_labels
give us longer form titles for the labels. (These labels are optional, but seem like a nice bonus feature.)This PR sets the stage for using conventional commits for semantic versioning. We want to validate before merging to
main
to determine the new release version.Task/Issue reference
Implements: #168