-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
ci: validate PR title against conventional commit rules #1262
ci: validate PR title against conventional commit rules #1262
Conversation
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.
Nice idea, thanks. Couple of changes suggested to the lists, based on #1252.
63d14d8
to
0b00e4c
Compare
Validated that this works: dimaqq#28 |
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.
Thanks!
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.
Thanks!
Looks good to me. I did not look at the upstream source to verify that it's not doing anything bad (particularly with the token we are providing) - I'm not super well placed to do that in JS. The upstream repo seems fairly healthy, which is a positive indicator.
As documented in canonical#1252 - types taken from the doc PR - scopes were scraped from project PR history
As documented in #1252