[python-committers] number of active core devs
tim.peters at gmail.com
Sun Jun 3 17:34:10 EDT 2018
[Victor Stinner <vstinner at redhat.com>]
> In short, the feature commit + fix the commit became a single commit :-)
I'd give a lot of weight to that - if I cared about counting commits at
all, which I don't ;-)
I just recently learned enough about git and github to get my feet wet
again. My first patch was to add some patterns to cpython's .gitignore to
stop worrying about garbage files unique to the editors I use (C.tom and
So I made a branch, created a push/pull/whatever_it's_called, and a
reviewer noted there was a better way to get what I was after (a local
git-ignore file that would apply to _all_ things I use git for).
So I closed the proposed change unmerged and deleted the branch.
In the old days, I would have just committed it, and then later reverted
the change after someone educated me.
So the github workflow is responsible for reducing my master commits 100%,
from 2 to 0 so far ;-)
And I think that's a good thing.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the python-committers