[python-committers] 4 weeks with the new workflow: what needs changing?
Ned Deily
nad at python.org
Tue Mar 14 20:29:59 EDT 2017
More information about the python-committers mailing list
Tue Mar 14 20:29:59 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 Mar 14, 2017, at 19:25, Barry Warsaw <barry at python.org> wrote: > On Mar 14, 2017, at 06:16 PM, Ned Deily wrote: >> There is one pattern that is happening fairly often and that I think we >> should do something about. That is, non-committers submitting a PR without >> first opening an issue on BPO. It gets very old fast trying to enforce that. >> Perhaps one of the bots could flag PRs that do not have a BPO ref in their >> titles? > Should there be a way to override that? In another project of mine on GH, we > use a 'trivial' tag on the PR to bypass that check. Sure, something like that would be fine. -- Ned Deily nad at python.org -- []
- 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