We do something similar to this, but we have a probot (probot.github.io/) that inspects the PR for file patterns and includes different checklists where relevant.
For instance, if there is a database migration it will include:
[ ] This PR appears to migrate the database schema, have you considered what indexes will be needed?
Or if a controller or model is changed:
[ ] This commit modifies a controller, are you sure that this commit does not break external API clients
I think this really helps with the utility of the checklist, otherwise it quickly turns into noise.
I'm a small business programmer. I love solving tough problems with Python and PHP. If you like what you're seeing, you should probably follow me here on dev.to and then checkout my blog.
We do something similar to this, but we have a probot (probot.github.io/) that inspects the PR for file patterns and includes different checklists where relevant.
For instance, if there is a database migration it will include:
Or if a controller or model is changed:
I think this really helps with the utility of the checklist, otherwise it quickly turns into noise.
Interesting. I had never heard of probot. I'll have to check it out.