No, I didn’t have to change to SSH - your solution worked.
For anyone else coming here with the same question who doesn’t want to wade through the thread, the steps that ultimately worked for me were:
- Followed the Authorise with github steps here
- Manually created new repo on the ACCESS Community Hub ACCESS Community Hub · GitHub
- Went into my experiment control directory and ran
git remote remove origin - Ran the below lines to push my experiments to new branches of the repo I created manually on the ACCESS Community Hub (in the second line). You probably won’t need the first line unless you’d run into prior difficulties like I did.
access-esm1-5-IP_m60is the local name for the remote repositoryhttps://github.com/ACCESS-Community-Hub/access-esm1.5-sst-perturbation-indo-pacificis the link to the manually-created repo on the ACCESS community Hubrelease-preindustrial+concentrationsis the current branch, identified withgit branchas per these instructionsgeorgyfalster-60pc_SST_variability_reductionis the new branch name
git remote remove access-esm1-5_IP_m60
git remote add access-esm1-5_IP_m60 https://github.com/ACCESS-Community-Hub/access-esm1.5-sst-perturbation-indo-pacific
git push access-esm1-5_IP_m60 release-preindustrial+concentrations:georgyfalster-60pc_SST_variability_reduction
And yes @lachlanswhyborn that sounds fine - I’ll put the SST preparation scripts on github and link that in the readme. Also no worries on the ‘no co-ownership’ - I was just thinking of a case where someone might have questions about the experiments but I’ve put my name in the branch name so they should be able to track me down.