Skip to content
GitTree
العربية
Remotes and sync

Choose remote credentials

GitTree runs your own Git, so fetch, pull and push sign in the way Git does on your computer: over HTTPS through your credential helper, over SSH with your key or SSH agent. Passwords and tokens stay in your system keychain, never in GitTree’s files.

FreeUpdated

Works in GitTree Free: every local Git feature, once you are signed in.

On this page
  1. Before you start
  2. Where to find it
  3. Steps
  4. Expected result
  5. Connected accounts
  6. If something goes wrong
  7. Questions
  8. Related

Before you start

  • A remote that needs you to sign in, such as a private repository.

Where to find it

  • Preferences › SSH for the SSH agent, a private key, unknown host keys and remembered passphrases.
  • Preferences › Integrations for connected hosting accounts.
ActionmacOSWindows and Linux
Preferences⌘,Ctrl+,

Steps

  1. Know which way your remote signs in

    A URL starting with https:// uses HTTPS credentials; one like git@github.com:… uses SSH. See it with Copy Remote URL (remotes).

  2. For HTTPS

    Git asks your credential helper. When Git needs a username, GitTree asks in its own window; the password or token is asked for by your system’s secure prompt.

  3. For SSH

    Use the SSH agent offers the keys your running SSH agent holds; GitTree never starts an agent. Or set one Private key for every SSH remote. Remember key passphrases keeps a passphrase in your keychain after you type it.

  4. Confirm a new server

    The first time you connect to a server, Connect to …? shows its fingerprint. Compare it with the one its owner publishes, then choose Connect and Remember Key.

Expected result

Fetch, pull and push sign in without asking again, with your secrets kept only in the keychain.

Connected accounts

With GitTree Pro or a running trial, a GitHub, GitLab, Bitbucket or Azure DevOps account you connect in Preferences › Integrations can also sign in for Git on that host. Your own SSH key or credential helper keeps working on Free.

If something goes wrong

“Auto-fetch skipped: … needs you to sign in.”

Background fetches never ask for credentials. Choose Fetch All once to sign in.

Permission denied (publickey)

The server did not accept any key offered. Add your public key on the host’s SSH keys page, load it into your agent, or set it as Private key.

Questions

HTTPS or SSH?

Both work. HTTPS with a token is easiest behind firewalls; SSH avoids tokens once your key is set up. Use whatever your Git already uses.

Related