Ok I think I have a workflow that I think will work. Perform the Authorise with Github and Push to Repo steps in one of the control directories, but don’t do the git push <repo_name> --all step. Once you’ve done that, go to the repository you’ve just created on ACCESS-Community-Hub (should be able to search that organisation by the repo_name you just used) and get the URL of the repository, we’ll call it <repo_URL>. Then do this in each of your other control directories:
git remote add origin <repo_URL>. This tells the current directory to point to the repository on Github as the “master” in a sense.- To check that this worked, do
git remote -v. It should show that URL forfetchandpush. git push --set-upstream origin <branch_name>. This should push the current control directory as a branch to the master with the given name. Say the directory you’re in is the 30% variability reduction case, the name it something like30pc_SST_variability_reduction.
Hopefully this works, I might have missed a step in there, so as always, let me know if there are problems.