I don’t know why it works for some cases but not other ones. You’ll need to do the push separately by using the -push option: git remote set-url -push origin don’t need to do anything further for pull because it does what fetch does (because pull is equivalent to fetch then merge). If the fetch URL has changed but the push URL has not, like this: origin (fetch) You may find that only fetch has changed - if so, the next section should help. Run git remote -v again and check the output.
If it is, run set-url again, making sure to exclude the ssh:// part of the URL. See if the SSH URL is prefixed with ssh://, like this: origin (fetch) If you do, check the output from git remote -v carefully. 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 (push) Troubleshooting Error: Could not resolve hostname This time, you’ll see something like this: origin (fetch) Then check what’s there again: git remote -v Type the following for BitBucket: git remote set-url origin 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 (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 MAC CHANGE PASSWORD 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.
#SOURCETREE MAC CHANGE PASSWORD PASSWORD#
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.I get stuck in the next step related to git lfs and public key:īatch request: Permission denied (publickey).: exit status 255error: failed to fetch some objects from ‘ ’Īnd this when checking out another branchĭownloading applications/synktest/assets/audio/audio_test_8sec_48khz.aac (8.4 KB)Įrror downloading object: applications/synktest/assets/audio/audio_test_8sec_48khz.aac (5c89c5e): Smudge error: Error downloading applications/synktest/assets/audio/audio_test_8sec_48khz.aac (5c89c5e4c943655d25c6fd4c5701ec0b5403a3675fc895db24dccc55a0ad1a7d): batch request: Permission denied (publickey).: exit status 255Įrrors logged to /Users/DinahmoeStudio/Documents/gitlab/dmafjs-video/.git/lfs/logs/Įrror: external filter ‘git-lfs smudge – %f’ failed 2Įrror: external filter ‘git-lfs smudge – %f’ failedįatal: applications/synktest/assets/audio/audio_test_8sec_48khz. I could now clone but have to enter the password several times It required the ssh passphrase which I had not tried
0 kommentar(er)
