Git Hosts & Authentication
vord uses your installed Git for local user repositories. It does not provide a token field, OAuth web view, app-password store, or force-push action.
Host support
Section titled “Host support”| Host | Recognition | Sign-in guidance | Git transport |
|---|---|---|---|
| GitHub | github.com, gist.github.com |
Optional gh auth login; otherwise System Git, GCM, Keychain, or SSH |
HTTPS or SSH |
| GitLab.com | gitlab.com |
Optional glab auth login; otherwise System Git, GCM, Keychain, or SSH |
HTTPS or SSH |
| Self-hosted GitLab | Can be labeled in the clone sheet | System Git, GCM, Keychain, or SSH; never a gitlab.com CLI action |
HTTPS or SSH |
| Bitbucket | bitbucket.org, bitbucket.com |
Generic GCM or SSH guidance; no app-password UI | HTTPS or SSH |
| Azure DevOps | dev.azure.com, *.visualstudio.com |
Generic GCM or SSH guidance | HTTPS or SSH |
| Other/self-hosted | Any other valid Git URL | System Git, GCM, Keychain, or SSH | HTTPS, SSH, or SCP-style SSH |
The official CLI actions are optional and appear only when the corresponding executable is installed. Authentication status comes from the CLI exit code; vord never reads a token. Repository-local credential.helper is reported only as “configured” — its value is never displayed.
Safe URLs and diagnostics
Section titled “Safe URLs and diagnostics”Do not put a username, token, or password into an HTTP(S) repository URL. vord rejects URL user information and credential query parameters such as token, access_token, private_token, oauth_token, or password before running Git. Git errors shown in the clone sheet and Inspector redact those query values, URL user information, known GitHub/GitLab token prefixes, password fields, and authorization headers.
Clone performs one direct attempt, without a preceding ls-remote. If it fails, the sheet keeps the input and explains the likely next action. See Managing Projects for the clone flow and Branches & Git Sync for push preflight.