{"id":11618,"date":"2017-07-20T13:40:21","date_gmt":"2017-07-20T13:40:21","guid":{"rendered":"https:\/\/www.process.st\/templates\/pull-request-review-failed-procedure\/"},"modified":"2024-02-28T20:45:54","modified_gmt":"2024-02-28T20:45:54","slug":"pull-request-review-failed-procedure","status":"publish","type":"post","link":"https:\/\/www.process.st\/templates\/pull-request-review-failed-procedure\/","title":{"rendered":"Pull Request Review Failed Procedure"},"content":{"rendered":"
\n

Introduction: <\/h2>\n
\n

This checklist describes the procedure for a developer to follow if their pull request has failed review. It involves thoroughly addressing the reasons for rejection, replying with information showing how you've re-tested and solved the problems, and then re-assigning the issue to a manager for a 2nd review.<\/p>\n

This simple process is most often used as part of the training and onboarding process at Process Street, and isn't commonly run more than a few times because it's easy to learn.<\/p>\n

See also our GitHub pull request process<\/a>.<\/p>\n<\/p><\/div>\n<\/section>\n

\n

Reply to every comment made in the GitHub PR <\/h2>\n
\n

Make sure that you reply to every comment that was added to the GitHub PR.<\/p>\n

This is so we can be sure that all issues were addressed and so that if anyone else looks at the PR, they will understand how the issues were resolved.<\/p>\n

Include a link to the pull request in the field below:<\/p>\n<\/p><\/div>\n<\/section>\n