[python-committers] Quick reminder: please don't push long-lived dev branches to the CPython repo
Terry Reedy
tjreedy at udel.edu
Fri May 25 16:19:18 EDT 2018
More information about the python-committers mailing list
Fri May 25 16:19:18 EDT 2018
- Previous message (by thread): [python-committers] Quick reminder: please don't push long-lived dev branches to the CPython repo
- Next message (by thread): [python-committers] Quick reminder: please don't push long-lived dev branches to the CPython repo
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 5/25/2018 1:43 PM, Brett Cannon wrote: > If you create a dev branch that is going to live for less than 24 hours > because you edited some typo in the docs or something through GitHub's > UI, then that's fine. But long-lived dev branches should be done in > one's personal fork. This is for two reasons: one is so that others > don't inadvertently download your dev branch when they do a `git pull` > (and because people often forget to do `git pull --prune`), --prune is not mentioned on https://devguide.python.org/gitbootcamp/ and two > because it eats up our CI (which is especially precious while we are > still on AppVeyor and the turn-around time there is so long).
- Previous message (by thread): [python-committers] Quick reminder: please don't push long-lived dev branches to the CPython repo
- Next message (by thread): [python-committers] Quick reminder: please don't push long-lived dev branches to the CPython repo
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the python-committers mailing list