Zachary Ware added the comment: > Multiple emails due to multiple branches - unfortunately won't, b/c each push > is against separate > branch and when processing that I don't know anything about related pushes.
Fair enough; if we can't do it, we can't do it [1]. Fixing the automatic closing and separate actions will go a long way toward alleviating the email flood. And of course the hg/git duplication is expected for now. Thanks for working on this! [1] Although, we could consider doing something heinous like checking if the latest message on the issue was a commit message and editing new commit information into it, but I did use the word "heinous" there for a reason :) _______________________________________________________ PSF Meta Tracker <metatrac...@psf.upfronthosting.co.za> <http://psf.upfronthosting.co.za/roundup/meta/issue611> _______________________________________________________ _______________________________________________ Tracker-discuss mailing list Tracker-discuss@python.org https://mail.python.org/mailman/listinfo/tracker-discuss Code of Conduct: https://www.python.org/psf/codeofconduct/
