4 ms·

Generic checklists for Pull Requests are great. It's easy to write a Tampermonkey script that lets you paste a prewritten checklist into a new blank PR descript

Generic checklists for Pull Requests are great. It's easy to write a Tampermonkey script that lets you paste a prewritten checklist into a new blank PR description, reminding you to do linting, run tests locally, and so on.

jaggederest 8y ago
https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/ https://help.github.com/articles/creating-a-pull-request-tem... You don't need to use a tampermonkey script, they support templates :)
rbongers 8y ago
I'll take this opportunity to recommend danger (https://github.com/danger/danger https://github.com/danger/danger) and danger-js (this is a rewrite of danger where most development is now being focused - https://github.com/danger/danger-js https://github.com/danger/danger-js). They allow you to automate checking your PR checklist on multiple platforms and automatically send reminders to people in the form of comments instead of replying yourself every time. It's different from other static analysis tools that integrate with pull requests for a few reasons: - It opens up a programming API, not just a configuration and rule system, which grants you more flexibility - It's tailored to send specific messages for errors so that you don't have to rely on the PR submitter to interpret errors and warnings - It also allows you to look at things like PR details and issue details, so you can check things like if a PR has an issue attached and much more - It's not restricted by language, so you can do things like check if someone updated a certain code file but did not update a certain markdown file and warn them that documentation may need to be updated Overall it just really cuts down on the endless cycle of submitter makes change > wait for reviewer to be available > reviewer gives feedback > wait for submitter to come back > submitter makes change. I really want more people to use it so it grows.

jaggederest 8y ago

https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/ https://help.github.com/articles/creating-a-pull-request-tem... You don't need to use a tampermonkey script, they support templates :)

rbongers 8y ago

I'll take this opportunity to recommend danger (https://github.com/danger/danger https://github.com/danger/danger) and danger-js (this is a rewrite of danger where most development is now being focused - https://github.com/danger/danger-js https://github.com/danger/danger-js). They allow you to automate checking your PR checklist on multiple platforms and automatically send reminders to people in the form of comments instead of replying yourself every time. It's different from other static analysis tools that integrate with pull requests for a few reasons: - It opens up a programming API, not just a configuration and rule system, which grants you more flexibility - It's tailored to send specific messages for errors so that you don't have to rely on the PR submitter to interpret errors and warnings - It also allows you to look at things like PR details and issue details, so you can check things like if a PR has an issue attached and much more - It's not restricted by language, so you can do things like check if someone updated a certain code file but did not update a certain markdown file and warn them that documentation may need to be updated Overall it just really cuts down on the endless cycle of submitter makes change > wait for reviewer to be available > reviewer gives feedback > wait for submitter to come back > submitter makes change. I really want more people to use it so it grows.