The discussion of automating the creation of cherry-pick PRs is at https://github.com/python/core-workflow/issues/8. And the requirement of the PR is to force people to go through CI to verify the cherry-pick took cleanly (and the Travis config is structured to only run the test suite if the PR changes things outside of Doc/; same goes for building the docs and code coverage is never waited on).
On Thu, 2 Mar 2017 at 16:02 Donald Stufft <don...@stufft.io> wrote: > Correct. Everything goes through a PR now. Ideally we will automate PRs > for backports. > > Sent from my iPhone > > > On Mar 2, 2017, at 7:00 PM, Yury Selivanov <yselivanov...@gmail.com> > wrote: > > > > > > > >> On 2017-03-02 6:36 PM, Donald Stufft wrote: > >> You no longer need approval from someone else and you can open a > cherry-pick PR prior to merging if you want. > > > > But I still can't push a cherry-picked commit without a PR for it? > > > > Yury > > _______________________________________________ > core-workflow mailing list > core-workflow@python.org > https://mail.python.org/mailman/listinfo/core-workflow > This list is governed by the PSF Code of Conduct: > https://www.python.org/psf/codeofconduct >
_______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct