You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
git lfs push --all origin main
Uploading LFS objects: 0% (0/3), 0 B | 0 B/s, done.
batch request: [email protected]: Permission denied (publickey).: exit status 255
but
ssh -T [email protected]
Enter passphrase for key 'C:\Users\*****':
Hi stephane-archer! You've successfully authenticated, but GitHub does not provide shell access.
so GitHub knows my public key but I can't use LFS, why?
I'm on Windows and git lfs push --all origin main does not ask for my passphrase
The text was updated successfully, but these errors were encountered:
Hey, I'm sorry you're having trouble. As this project is just for the open-source Git LFS client, you may also want to contact GitHub's support team, as they can provide advice specific to GitHub's services.
That said, if you give us some more detail, we may be able to help. See our "other issue" template for the things we usually ask for:
The output of git lfs env, when run within the working tree of the repository you're using.
The output of git config -l may be helpful as well; just make sure to remove any private information first.
I would also recommend providing the output (with any private information removed) from running your git lfs push command with the environment variables GIT_TRACE=1 GIT_TRANSFER_TRACE=1 GIT_CURL_VERBOSE=1 set.
As we haven't heard anything more regarding this issue, I'm going to close it, but if you're still having a problem we can help with, please re-open the issue and provide some of the details I mentioned above.
You might also want to take a look at some of the recent discussion in #5784, just in case the lfs.ssh.autoMultiplex=false setting would help you here too.
but
so GitHub knows my public key but I can't use LFS, why?
I'm on Windows and
git lfs push --all origin main
does not ask for my passphraseThe text was updated successfully, but these errors were encountered: