We use a GitHub Project named Code Reviews to organize our work. It has several columns, including Work In Progress and Ready For Initial Review. We've enabled automation to make life easier (e.g. requesting changes will automatically move a PR to the Work In Progress column, which is amazing).
We want to give PR authors some control over the placement of their PRs in this Project. Specifically, it would be great if a PR author could move their own PR to either the Work In Progress or Ready For Initial Review column, regardless of its current location. (Because PR authors can push changes to their own branches, this indicates whether they're actively working on a PR, or whether they're waiting for maintainer review.)
GitHub Actions/Workflows may be capable of this. #829 (reverted by #847) was doomed because PRs from forks (i.e. all of our PRs) don't have access to secrets in the base repo. However, perhaps there could be a workaround, like a PR author could comment in an issue "/wip GH-nnn" or "/review GH-nnn" and a workflow would compare the commenter and the PR's submitter, and move the card if they match. I don't know if that would be doomed too, but presumably there would be no security concerns for a workflow running on issue comments (since only the base repo is involved there).
Suggested by Michael Schellenberger Costa (@miscco) in #921 (comment).
We use a GitHub Project named Code Reviews to organize our work. It has several columns, including Work In Progress and Ready For Initial Review. We've enabled automation to make life easier (e.g. requesting changes will automatically move a PR to the Work In Progress column, which is amazing).
We want to give PR authors some control over the placement of their PRs in this Project. Specifically, it would be great if a PR author could move their own PR to either the Work In Progress or Ready For Initial Review column, regardless of its current location. (Because PR authors can push changes to their own branches, this indicates whether they're actively working on a PR, or whether they're waiting for maintainer review.)
GitHub Actions/Workflows may be capable of this. #829 (reverted by #847) was doomed because PRs from forks (i.e. all of our PRs) don't have access to secrets in the base repo. However, perhaps there could be a workaround, like a PR author could comment in an issue "/wip GH-nnn" or "/review GH-nnn" and a workflow would compare the commenter and the PR's submitter, and move the card if they match. I don't know if that would be doomed too, but presumably there would be no security concerns for a workflow running on issue comments (since only the base repo is involved there).
Suggested by Michael Schellenberger Costa (@miscco) in #921 (comment).