[python-committers] 4 weeks with the new workflow: what needs changing?
Brett Cannon
brett at python.org
Thu Mar 16 12:14:54 EDT 2017
More information about the python-committers mailing list
Thu Mar 16 12:14:54 EDT 2017
- Previous message (by thread): [python-committers] 4 weeks with the new workflow: what needs changing?
- Next message (by thread): [python-committers] 4 weeks with the new workflow: what needs changing?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Wed, 15 Mar 2017 at 17:03 Barry Warsaw <barry at python.org> wrote: > On Mar 16, 2017, at 12:00 AM, Brett Cannon wrote: > > >But that would require that external contributors know to set that label > >ahead of time and I'm willing to bet most won't. > > Not if the test has a retry feature. Your change is trivial but you didn't > add the label. The test fails. You add the label and retry the test. > Now it > passes. > Ah, you didn't say you wanted this to be a status check. :) Do we want to go so far as that rather than a comment or PR template? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20170316/c13a40a1/attachment.html>
- Previous message (by thread): [python-committers] 4 weeks with the new workflow: what needs changing?
- Next message (by thread): [python-committers] 4 weeks with the new workflow: what needs changing?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list