-
Notifications
You must be signed in to change notification settings - Fork 22.5k
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
PR hygiene checking #910
PR hygiene checking #910
Conversation
https://github.com/marketplace/actions/conventional-pr-title-alt might be another interesting option Edit: or one of these https://github.com/marketplace?type=actions&query=title |
I looked at most of those and didn't feel attracted to any of them. They all seemed overly complicated or just not perfect. And besides, I quite like the idea of building it "from scratch" because then you're limitless in what you want to implement. Our current logic is a bit odd in that it's so oddly specific. And we can now quite easily express our business logic with simple string-checking if-statements in JavaScript rather than custom regexes in a Yaml file. |
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.
This seems like a good start to me, thanks @peterbe!
ping @fiji-flo |
One thing I've found for myself is that when I do a lot of flaw fixing PRs, I never type in a description. Because it's rarely useful when the summary is sufficient. |
This looks ready to merge (from a CI point of view) |
cb612f4
to
5574b25
Compare
I changed my mind. I made it less controversial so that it doesn't require that the description is non-empty. |
@fiji-flo Do you mind if I merge without your review? |
fixes #782
Here's what it looks like if the PR title was
Update index.html
And if all is well:
Not rocket science but hopefully a start.