I investigated the cpython approach and the PR labelling is a part of the existing bedevere bot which does a number of things (not all relevant to Arrow). Yesterday I created a standalone Github action[1] dedicated to this task roughly based on my previous email. It will apply "awaiting-review" and "awaiting-changes" labels when appropriate. I think it's probably ready to try out at this point (I'm sure there will be some hiccups). If any repo wants to volunteer to be a guinea pig I will work with you and get the action configured and running. I have it enabled on a dummy repository here[2] and this is what it looks like in action[3].
[1] https://github.com/westonpace/pr-needs-review/ [2] https://github.com/westonpace/pr-needs-review-dummy-2/blob/main/.github/workflows/label-pr.yml [3] https://github.com/westonpace/pr-needs-review-dummy-2/pull/13 On Thu, Jul 1, 2021 at 11:36 AM Adam Lippai <a...@rigo.sk> wrote: > > Not sure if it's applicable, but GitHub is improving: > https://github.blog/changelog/2021-06-23-whats-new-with-github-issues/ > > That spreadsheet-like issue tracking looks concise. > > Best regards, > Adam Lippai > > On Wed, Jun 30, 2021, 10:28 Antoine Pitrou <anto...@python.org> wrote: > > > > > Le 30/06/2021 à 10:04, Wes McKinney a écrit : > > > > > > I guess my concern with this is how to quickly separate out "PRs I am > > > keeping an eye on". If there are 100 active PRs and only 20 of them > > > are ones you've interacted with, how do you know which ones need your > > > attention? GitHub does have the "reviewed-by" filter which could be > > > good enough > > > > There's also the "involves" filter that can also select PRs you have > > commented on without giving a formal review. > > > > However, those filters don't let you know which PRs are pending review > > if you haven't already commented on them. > > > > Regards > > > > Antoine. > >
