git / ssh agent / 1password

[ZachBurm]

Hey @haydenull,

I am trying to track down the source in the logseq repo for the new git command since execGitCommand was deprecated because I use 1Password to manage my SSH keys and the 1pass agent for git via ssh. This is causing failures in using the key for signing or pushing to the repo and I am hoping to solve it myself with a PR, but need some assistance in finding the source of the git commands? I am new to the logseq project so don't know my way around the source code yet.

Thanks!

[aeshna-cyanea]

is this it? https://plugins-doc.logseq.com/logseq/Git/execCommand it links to the function in the logseq source (changed link to master) which in turn links to the command documentation in dugit

[davad]

I'm having the same issue with ssh-agent and Bitwarden.

[D-VR]

since this is one of the only results for SSH agent issues involving logseq on google, I want to post a possible solution for commit issues involving the logseq flatpak.
(i.e. [Git] fatal: cannot exec '/opt/1Password/op-ssh-sign': No such file or directory)

By default logseq flatpak has permissions to use the SSH Auth socket (so if you have your SSH agent correctly setup it should just work! See this: https://developer.1password.com/docs/ssh/agent/compatibility/#ssh-auth-sock ), however for commit signing (with i.e. a SSH key using 1Password) you need to give it permission to read the 1Password SSH sign command

Adding this filesystem permission in Other files in Flatseal is enough to fix the issue:
/opt/1Password/op-ssh-sign:ro

Please be aware that the exact path is dependent on where your 1Password was installed. You can find the folder using:
ls -l $(which 1password)