[python-committers] 4 weeks with the new workflow: what needs changing?
Paul Moore
p.f.moore at gmail.com
Sun Mar 12 07:37:21 EDT 2017
On 10 March 2017 at 22:13, Brett Cannon <brett at python.org> wrote:
> Fifth, anything I missed? :)
One thing, somewhat peripheral. Since the move, issues on bpo now get
PRs added to them. That's fine, but it further reduces the signal to
noise ratio on the emails sent out for an issue (it was always bad,
with emails sent every time someone added or removed themselves from
the nosy list, and things like that, this just makes things a little
worse). Ideally, I'd like to only get emails when new messages are
added to the issue, but I don't think that's possible.
I don't have a problem with the new "PRs attached to this issue" field
- that's of course important to have. But is there any way to not have
them generate emails (probably on a per-user basis, as I'm sure
there's people who appreciate emails when PRs are added)? I guess the
other option is a client-side filter, but I'm not sure how easy it
would be to do something like that.
Paul
More information about the python-committers
mailing list