[Victor Stinner <vstin...@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 *.bak). 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.
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
