> Maybe others have different workflows, but I don't see much of a need for > keeping your fork's main branch up to date. My workflow is something like > this: > > % git remote -v > origin g...@github.com:JelleZijlstra/cpython.git (fetch) > origin g...@github.com:JelleZijlstra/cpython.git (push) > upstream https://github.com/python/cpython.git (fetch) > upstream https://github.com/python/cpython.git (push) > % git checkout main > Already on 'main' > Your branch is up to date with 'upstream/main'. > % git pull > ... get new changes from upstream > % git checkout -b myfeature > ... write my code > % git push -u origin myfeature > ... open a pull request > > So my local main branch tracks upstream/main (the real CPython repo), not > origin/main (my fork).
Thanks. Up until the 3.10 split I was tracking main from a development branch in my fork, and trying — lately pretty much unsuccessfully — to drink from the firehose of changes to the virtual machine code. It made sense to me to keep my fork's main up-to-date with upstream/main. Now that I have diverged to follow the 3.10 branch for now, that's less of an issue. Skip _______________________________________________ Python-Dev mailing list -- python-dev@python.org To unsubscribe send an email to python-dev-le...@python.org https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/python-dev@python.org/message/Y6KZJPLQJNGXII7YBHTU7ICESICELL7V/ Code of Conduct: http://python.org/psf/codeofconduct/
