On Sun, Jul 10, 2016 at 4:33 PM, Senthil Kumaran <sent...@uthcode.com> wrote: > On Sun, Jul 10, 2016 at 12:15 AM, Nick Coghlan <ncogh...@gmail.com> wrote: >> >> I don't see any problem with doing that early - we already carry a >> .gitignore file for the benefit of folks using hg-git bridges, so if we >> wanted to start experimenting with GitHub workflows (including things like >> Travis CI), why gate that on actually doing the migration first if we can >> use the existing mirrors for it? > > > I am in favor of introducing this before the migration. It seems like > an easy thing to setup without any clutter to the existing setup. > For e.g, for the pull request template, We can have the > PULL_REQUEST_TEMPLATE.md as suggested by Carol inside a .github > directory in hg repo and communicate our intention. That should > address one of the points in this thread.
I'm not sure how that would solve the main problem: People do not like to read project descriptions and contribution guides :) python/cpython description already states that it's a read-only mirror of the Mercurial repository and it took me a second to realize that python-git/python is a way outdated mirror of the old SVN repository. I'd propose to set a webhook that will close all pull requests automatically (with a short informative message) on python/cpython. I'm planning to finish my merge bot this month so I can write a simple webhook quickly if needed. --Berker _______________________________________________ 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
