Please make sure you have the correct access rights You might get this error: ssh: Could not resolve hostname :username: nodename nor servname provided, or not knownįatal: Could not read from remote repository. Origin :username/reponame.git (push) Troubleshooting Error: Could not resolve hostname This time, you’ll see something like this: origin :username/reponame.git (fetch) Then check what’s there again: git remote -v Type the following for BitBucket: git remote set-url origin :username/reponame.gitįor GitHub, replace with. You can see that the URLs include the protocol. This example shows a repo on BitBucket GitHub is similar. You should see a pair of entries for each remote repo (I once had origin and origin2, but that’s another story): one for fetch, which includes pull, and one for push: origin /username/reponame.git (fetch) Then check to see what you have on your server already: git remote -v Open Terminal or your command-line app of choice and navigate to your repo’s directory: cd ~/projects/reponame This is how you tell your Git server how you want to access it. This rigmarole needs to be done on each computer you intend to access your Git repo with for each repo you have that you want to access by SSH rather than by HTTPS.
#Sourcetree github ssh how to
Here, I outline how to do it on Mac OS X, partly to remind myself how to do it in the future, partly to collate all the infomation on the internet about it and partly in the hope that someone else might find it useful.
I seemed to spend a crazy amount of time trying to work out how to change access to a Git repository (repo) from HTTPS to SSH to avoid password prompts when pushing changes to BitBucket and GitHub. Add the private SSH key to your keychain.Add the public SSH key to your remote Git server.
0 kommentar(er)
