[python-committers] New workflow - some questions
Paul Moore
p.f.moore at gmail.com
Fri Jul 28 15:42:21 EDT 2017
More information about the python-committers mailing list
Fri Jul 28 15:42:21 EDT 2017
- Previous message (by thread): [python-committers] AppVeyor was unable to build non-mergeable pull request
- Next message (by thread): [python-committers] New workflow - some questions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I'm just looking at doing some work for the first time under the new workflow. Most things look fine - I'm familiar with git/github, so there's nothing startling in there, but I do have a few small questions: 1. Section 32.2 in the Git bootcamp section - is there any reason to use git at github URLs for the clones? I normally always use https://github.com URLs, as they work with my proxy at work. 2. Section 32.10, I generally use "Compare and create pull request" from my clone's github page, as that seems simpler. Is there any reason for starting from the cpython repo - the process working that way (which I wasn't even aware of!) seems more complex. I can't see that it matters much, but I wouldn't want to mess up a PR if there *is* a difference in the results. 3. The new blurb tool - I presume I'll need to set that up somewhere/somehow, and use it to create a news entry. But I can't find any docs on it at all :-( There may be other stuff - I've been watching the core-workflow list, and it feels like there's some awfully complex stuff being discussed. But so far it looks pretty straightforward and "as expected" - which is a credit to Brett and the others who've set all this up! Thanks, Paul
- Previous message (by thread): [python-committers] AppVeyor was unable to build non-mergeable pull request
- Next message (by thread): [python-committers] New workflow - some questions
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list