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"
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 wrote:
>
> Le 30/06/2021 à 10:04, Wes McKinney
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
On Tue, Jun 29, 2021 at 8:05 PM Weston Pace wrote:
>
> I apologize. I did plan on working on this but it's taken a back seat
> for a while. I would still recommend shying away from a standalone
> UI. You will end up making a lot of requests (and possibly running
> into Github throttles) if you
I apologize. I did plan on working on this but it's taken a back seat
for a while. I would still recommend shying away from a standalone
UI. You will end up making a lot of requests (and possibly running
into Github throttles) if you want detailed PR information for all of
the PRs. To work
Le 29/06/2021 à 15:25, Wes McKinney a écrit :
On Tue, Jun 29, 2021 at 3:10 PM Andrew Lamb wrote:
The thing that would make me more efficient reviewing PRs is figuring out
which one of the open reviews are ready for additional feedback.
Yes, I think this would be the single most
I review a decent number of PRs for Apache Beam, and I've built some of my
own tooling to help keep track of open PRs. I wrote a script that pulls
metadata about all relevant PRs and uses some heuristics to categorize them
into:
- incoming review
- outgoing review
- "CC'd" - where I've been
I just had a quick chat over the ASF's slack with Daniel Gruno from the
infra team and they are rolling out the "triage role" [1] for
non-committers, which AFAIK offers useful tools in this context:
* add/remove labels
* assign reviewees
* mark duplicates
* close, open and assign to issues and
On Tue, Jun 29, 2021 at 3:10 PM Andrew Lamb wrote:
>
> The thing that would make me more efficient reviewing PRs is figuring out
> which one of the open reviews are ready for additional feedback.
Yes, I think this would be the single most significant quality-of-life
improvement for reviewers.
>
The thing that would make me more efficient reviewing PRs is figuring out
which one of the open reviews are ready for additional feedback.
I think the idea of a webapp or something that shows active reviews would
be helpful (though I get most of that from appropriate email filters).
What about a
hi folks,
I've noted that the volume of PRs for Arrow has been steadily
increasing (and will likely continue to increase), and while I've
personally had less time for development / maintenance / code reviews
over the last year, I would like to have a discussion about what we
could do to improve
11 matches
Mail list logo
