[python-committers] Quick reminder: please don't push long-lived dev branches to the CPython repo (original) (raw)
Brett Cannon brett at python.org
Mon May 28 12:19:04 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] [Python-Dev] Troubles to merge changes in the 2.7 branch: PR "out-of-date" branch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, 25 May 2018 at 14:01 Steve Dower <steve.dower at python.org> wrote:
On 25May2018 1043, Brett Cannon wrote: > (and because people often forget to do
git pull --prune), 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).Don't we have branch filters on CI? (I certainly put them on the VSTS builds, and I thought they were there on AppVeyor/Travis too.)
We have filters for Travis, not sure about AppVeyor. I think the branch that triggered this was also immediately opened as a PR and pushing to the branch updates the PR and so that also didn't help matters either.
But regardless, making everyone download the branch is still a bit annoying
-Brett
Cheers, Steve -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.python.org/pipermail/python-committers/attachments/20180528/3d895c80/attachment.html>
- 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] [Python-Dev] Troubles to merge changes in the 2.7 branch: PR "out-of-date" branch
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]