Remotes & Syncing
Fetch, pull and push options, ahead/behind badges, auto-fetch, and HTTPS/SSH credentials
GitBor keeps the everyday sync controls in the toolbar above the graph and the credential management in Repository Settings.
Fetch, pull, push
| Action | Options |
|---|---|
| Fetch | Fetches all remotes. You can also fetch a single remote from its context menu in the sidebar. |
| Pull | The main button pulls the current branch; the ▾ split adds Pull --rebase. Uncommitted changes are auto-stashed and restored around the pull. |
| Push | The main button pushes; the ▾ split adds Push --force and, when the branch has no upstream, Push -u origin to set it. |
The Pull and Push buttons carry badges: the Pull badge is how many commits you're behind the upstream, the Push badge is how many you're ahead. They come straight from the tracking-branch comparison, so they mean exactly what git status would tell you.
Auto-fetch
GitBor periodically fetches in the background and tells you when there are new commits on the remote ("3 new commits on remote"). If the network is unavailable it pauses auto-fetch and retries on a timer; you can Retry now at any time. When several repositories fail to reach their remotes at once, the errors are aggregated into a single notice with a Show details expander instead of a wall of popups.
HTTPS credentials
Repository → Repository Settings… → Remote access (HTTPS) manages the username and password/token for an HTTPS remote:
- Save credentials stores them via your configured Git credential helper. Old credentials for that remote are cleared first — useful right after a corporate password or PAT rotation.
- Reset saved credentials clears them.
If no credential helper is configured (credential.helper), GitBor warns that the password won't be stored and Git will keep asking — configure Git Credential Manager first. If the remote uses SSH, there's no HTTPS password to manage and GitBor points you to the SSH key manager instead.
SSH keys
For SSH remotes, manage keys from Repository Settings → SSH keys (global, in ~/.ssh). You can list key pairs, generate a new Ed25519 (recommended) or RSA key with an optional passphrase, copy a public key to paste into GitHub/GitLab/Bitbucket, and delete keys. Full details in Settings.
When a push or pull fails
GitBor classifies common failures and shows a focused dialog with the right next step instead of raw Git errors — for example a diverged remote (pull or rebase first), an authentication failure, a network error, or a held index.lock. These are covered in Data Protection → Error handling.