[core-workflow] The peps repo has been migrated!

[Ian Lee]

Not speaking from any sort of official position, but you could do a push to
a separate branch that you deleted after you verify it worked.

E.g.

$ git clone https://github.com/python/peps.git
$ cd peps
$ git checkout -b foo
# edit something
$ git commit -a -m"test commit"
$ git push origin foo
# verify it worked through github website worked
$ git push --delete origin foo

Cheers,

Ian

On Thursday, June 16, 2016, Antoine Pitrou <solipsis at pitrou.net> wrote:

> On Wed, 15 Jun 2016 22:56:35 +0000
> Brett Cannon <brett at python.org <javascript:;>> wrote:
> > Python's PEPs now officially live at https://github.com/python/peps .
> >
> > Thanks to Donald Stufft for the infrastructure stuff, Kushal Das for
> > pushing me at the PyCon US sprints to get this going, Senthil Kumaran for
> > the migration tool, and everyone else who has helped somehow in making
> this
> > happen.
> >
> > I'll be updating PEP 512 -- on GitHub! -- to reflect this. That will make
> > the devguide the next repo to migrate.
>
> I might have missed something, but is there a test repo to test e.g.
> push permissions? I don't want to add a dummy changeset to the peps repo...
>
> Regards
>
> Antoine.
>
>
>
> _______________________________________________
> core-workflow mailing list
> core-workflow at python.org <javascript:;>
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
>


-- 

~ Ian Lee | IanLee1521 at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/core-workflow/attachments/20160616/19653576/attachment.html>