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

2017-06-18 Thread Brett Cannon
On Sat, 17 Jun 2017 at 18:11 Nick Coghlan wrote: > On 18 June 2017 at 05:07, Brett Cannon wrote: > > The stages I see are: > > > > 1. Awaiting first review: no one has reviewed the PR > > I'd just make this "Awaiting review", +1 to the simplification of the name. > and have it advance only f

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

2017-06-18 Thread Mariatta Wijaya
On Sun, Jun 18, 2017 at 9:36 AM, Brett Cannon wrote: > At some point in the future, we >> could potentially even go to an OpenStack style flow where Bedevere >> actually *merges* patches in this state if their CI run succeeds, > > One concern is about cleaning up the commit message before merging

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

2017-06-18 Thread Brett Cannon
On Sun, Jun 18, 2017, 09:56 Mariatta Wijaya, wrote: > > On Sun, Jun 18, 2017 at 9:36 AM, Brett Cannon wrote: > >> At some point in the future, we >>> could potentially even go to an OpenStack style flow where Bedevere >>> actually *merges* patches in this state if their CI run succeeds, >> >> >