[core-workflow] Github Mirrors - Should Disallow Pull Request / Issue Creation Until the migration

[Carol Willing]

![](https://link.nylas.com/open/1oeantoc6n5zav9mkp4e6rmlq/local-
896ba456-d22b?r=Y29yZS13b3JrZmxvd0BweXRob24ub3Jn)

On Jul 10 2016, at 7:20 am, Berker Peksağ <berker.peksag at gmail.com>
wrote:  

> On Sun, Jul 10, 2016 at 4:33 PM, Senthil Kumaran <senthil at uthcode.com>
wrote:  
> > On Sun, Jul 10, 2016 at 12:15 AM, Nick Coghlan
<ncoghlan at 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 :)

  
The template is a simple courtesy to alert those opening a PR on the repo that
it's not the right place. Of course, people might still not read it ;-)  

  

>  
>

>

> 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.

  

Sure, that's helpful for the maintainers too. The template saves a potential
contributor the embarassment/frustration of opening a PR just to have it
closed moments later.

  

>  
>

>

> \--Berker  
>

> _______________________________________________  
> core-workflow mailing list  
> core-workflow at 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160710/4ef50a1b/attachment.html>