56f2295e6ea44c07b8132cb5e0c303c644e1544c
The T3 threads could clone from gitea interactively (m3tam3re terminal) but not from the t3code service context. Instead of guessing which link in the spawn chain drops HOME, make every link irrelevant: - t3SshConfig: absolute IdentityFile (no ~ resolution needed) - service env: HOME set explicitly + GIT_SSH_COMMAND pointing at the absolute store-path ssh config — git uses exactly this config for gitea remotes regardless of HOME or user ssh-config lookup Verified via nix eval: HOME=/home/m3tam3re and GIT_SSH_COMMAND=ssh -F /nix/store/...-t3-gitea-ssh-config land in the unit. After deploy: systemctl restart t3code, then retrigger the clone thread.
Languages
Nix
87.5%
JavaScript
6.7%
Shell
5.8%