raulcd opened a new issue, #33977:
URL: https://github.com/apache/arrow/issues/33977

   ### Describe the enhancement requested
   
   I would like to start working on some automation for our PRs  workflow.
   
   I've heard, and have experienced, the frustration to spend 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.
   
   An example of a great improvement is the 
[CODEOWNERS](https://github.com/apache/arrow/pull/33622). This allows us to use 
filters like `is:pr is:open user-review-requested:@me` 
https://github.com/apache/arrow/pulls?q=is%3Apr+is%3Aopen+user-review-requested%3A%40me+
   
   The above filter 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 (commits / 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.
   
   ### Component(s)
   
   Developer Tools


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to