Reviewer Follow Ups

[0x4007]

Sometimes reviewers are slow and the follow ups will keep pinging the assignee even though they are finished with their work.

This will require us to change our standard operating procedure to convert back to draft pull request if we think the pull is not ready to go. This I am hesitant for because if it's a private repo then they must pay for GitHub premium to support draft pulls. Perhaps we can incorporate some logic for when we request changes, then we know the pull is not ready. We can discuss.

--

If the pull is ready then it should follow up with reviewers. If it isn’t ready (draft) then it should follow up with the assignee(s).

If the contributor stops working on the task they will be reminded. Either they should unassign themselves, continue working, or convert the draft to a finalized pull.

https://t.me/UbiquityDevPool/2960

[0x4007]

Related #48