-
Notifications
You must be signed in to change notification settings - Fork 15
chore: [DevOps] PR Title Linter #273
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
Conversation
| on: | ||
| pull_request_target: | ||
| types: | ||
| - opened | ||
| - edited | ||
| - synchronize |
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.
(Comment/Opinion)
I didn't expect this syntax to be mandatory.
- It may discourage future, external contributors.
- It may break current and future automated PRs.
It's not possible to make this more like a warning/notification right?
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.
more like a warning
No, at least not per the docs. I checked that it works with Dependabot, but Release PRs would currently fail. Updated the script ✅. For external contributors it should be fine, because it is easy to fix and only occurs after a PR is already raised, i.e. when most of the work is already done.
Examples which are allowed:
chore: [DevOps] PR Title Linterchore: [DevOps] pr title linterchore: PR Title LinterExamples which are not allowed:
PR Title Linter[DevOps] PR Title Linterchore: [Foo] PR Title LinterTested on my fork