Gitlo

Accounts and hosting

GitHub, GitLab, Gitea, Bitbucket, Azure DevOps and self-hosted servers.

Connect an account

Open Paramètres › Comptes (Settings › Accounts, Ctrl ,) and paste a personal access token. Gitlo checks it with the hosting service, then saves it in your system keychain: Credential Manager on Windows, Keychain on macOS, libsecret on Linux.

Gitlo works out which service hosts a repository from its remote URL.

Enterprise and self-hosted servers

Add GitHub Enterprise, a self-hosted GitLab or a Gitea server in Paramètres › Comptes (type and host name). Each server has its own session and token. Add gitea.com the same way as any other Gitea server.

Not supported yet: a server installed under a subpath (example.com/gitlab/), or an SSH host that differs from the web host.

What you get

  • Pull / merge requests (Ctrl 3): list, create, check out locally (forks included, into a pr/N or mr/N branch) and CI status.
  • CI/CD (Ctrl 4): GitHub Actions runs, GitLab pipelines and Gitea Actions, with jobs and their logs in collapsible steps. You can re-run or cancel a run, except on Gitea (read-only). The view refreshes every 10 s while a run is in progress.
  • Issues: a #123 badge on branches linked to an issue, and Nouvelle branche depuis une issue (new branch from an issue).
  • Author avatars. You can turn them off: to fetch them, Gitlo sends the author’s email address to the hosting service.
  • Clone straight from your account.