My apologies, my Google/GitHub-fu has failed me, so I resort to asking this community for help (an uncommon, perhaps first-time, experience). I worry that I’m doing this all wrong. Please steer me right if I am.
I forked the Python main repo awhile ago (couple years maybe?), before the 3.7 branch was created. 3.7 is now in beta, so the 3.7 branch was created. The two repos in question are:
I followed the instructions here to keep the latter in sync with the former:
but it still lacks a 3.7 branch, both on the web and locally. I captured those instructions in a trivial shell script:
git fetch upstream git co master git merge upstream/master echo "now push when ready"
Here’s a trimmed example of git br -a:
% git br -a * master remotes/origin/3.5 remotes/origin/3.6 ... others, but no 3.7 ... remotes/upstream/2.7 remotes/upstream/3.4 remotes/upstream/3.5 remotes/upstream/3.6 remotes/upstream/3.7 ... remotes/upstream/master
How do I create a remotes/origin/3.7 branch which will track remotes/upstream/3.7? Is there some combinations of shell level git commands which will accomplish this, or do I need to manually edit .git/config? This will be an ongoing problem as new 3.x releases of Python approach. It would be great if I could automatically create new 3.x branches in remotes/origin as they appear in remotes/upstream…