Hi, I would like to start working on some automation for our PRs and issues workflows.
I've heard, and have experienced, the frustration of spending a lot of time on our issue tracker and our PRs to follow up on their status. It is very hard to keep track of which PRs and issues are waiting for user feedback, have gone stale or are pending maintainer/committer action. This means users frequently get no timely response, all the while we regularly spend time on GH to look for PRs / issues needing action from us. As a first step we should probably tackle PRs, once PRs are tackled and we are satisfied with the solution, we can try to devise a similar one for GH issues. An example of a great improvement is the CODEOWNERS addition [1]. This allows us to use filters like `is:pr is:open user-review-requested:@me` [2] which will show PRs that have requested a review from us. This does not solve the problem of what are the PRs waiting for second review, waiting for changes, etcetera. I don't think we have to reinvent the wheel, CPython has something that works well and can easily be adapted/tweaked. They use a GitHub bot (bedevere) with the following state machine: https://github.com/python/bedevere#pr-state-machine PRs have one label of the following workflow labels, depending of the state: - `Awaiting review` - `Awaiting core review` - `Awaiting changes` - `Awaiting change review` - `Awaiting merge` I would like to propose adding a GitHub bot to our repo that triggers on PR changes / comments implementing a similar workflow than the one on the CPython repository. I am going to start working on it and I would love to hear feedback about that workflow. I have also created an issue on the Repo [3]. Kind regards, Raúl [1] https://github.com/apache/arrow/pull/33622 [2] https://github.com/apache/arrow/pulls?q=is%3Apr+is%3Aopen+user-review-requested%3A%40me+ [3] https://github.com/apache/arrow/issues/33977
