> On Jun 15, 2016, at 6:55 PM, M.-A. Lemburg <m...@egenix.com> wrote: > > On 16.06.2016 00:48, M.-A. Lemburg wrote: >> On 16.06.2016 00:42, Brett Cannon wrote: >>> I don't think anything has fallen over, so I'm calling this a successful >>> migration! The peps repo is now https://github.com/python/peps . >> >> Thanks for putting so much hard work into this ! > > BTW: Is it ok to push directly into the PEP repo or should we > (as PEP authors) always go through PRs which we then merge into > the repo ? >
Currently there’s nothing preventing people from pushing directly to the PEP repository, in https://github.com/python/peps/issues/5 there’s talk of setting up Travis to ensure the PEPs are always building and if the flag is set to require a +1 from Travis, then all changes will need to go through PRs. — Donald Stufft _______________________________________________ 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/
