On Sun, 12 Feb 2017 at 04:26 Serhiy Storchaka <storchaka+cpyt...@gmail.com> wrote:
> неділя, 12 лютого 2017 р. 11:46:08 EET Paul Moore написано: > > ... and just a further note that I'm finding the new github PR > > messages much easier to follow than the old python-checkins traffic. > > That's probably nothing more than personal familiarity with github, > > but nevertheless, even after only a couple of days, the new workflow > > is showing benefits for me. So thanks again! > > In contrary, I'm finding the new github PR messages less useful than old > messages. > > 1. The subject now starts with longer common prefix. It contains constant > "[python/cpython]" rather then shorter "cpython" and a part of the hash > which > is less useful for reader (and in any case is duplicated in the message > body). > > 2. The subject no longer contains information about a branch and merge > status. > > 3. The sender name is GitHub rather than the name of committer. > > 4. The body doesn't contain full diff. It was easier to look at inlined > patch > in mail/news client rather than open separate window in browser. > > Is this configurable? I would prefer restoring the old format. > The GitHub service we are using isn't configurable. If you can find an appropriate integration or service at https://github.com/integrations then we could consider swapping the services.
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
