[core-workflow] Auto labeling PRs based on what stage they're in

[Brett Cannon]

On Mon, Jun 19, 2017, 18:15 Nick Coghlan, <ncoghlan at gmail.com> wrote:

> On 20 June 2017 at 03:39, Brett Cannon <brett at python.org> wrote:
> > OK, here is a dot graph that lays out the stages and the flow between
> them
> > based on what has been discussed so far. You can use
> > http://www.webgraphviz.com/ to view the graph in a browser. Anything
> green
> > requires/blocks on a core dev, blue requires/blocks on the PR creator,
> and
> > orange is open to anyone.
>
> This looks good to me. I also think there are a few extra exceptional
> flows, but we can probably say "manipulate the labels directly" for
> these:
>
> "Awaiting changes" -> "Awaiting merge": Core dev implements changes
>

They could change their review to handle this.

themselves and pushes to submitter's branch
> Core dev PR -> "Awaiting core review"
>

Yeah, that could be manual.

Core dev PR -> "Awaiting changes"
>

If this is due to a review from a core dev then it's just like any other
core review as you don't want to ignore such a review.

-Brett


> Cheers,
> Nick.
>
> --
> Nick Coghlan   |   ncoghlan at gmail.com   |   Brisbane, Australia
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20170620/20133181/attachment-0001.html>