GitLane v2.6.0

Also in the docs: Accounts and identities

What's changed

Accounts and sign-in (#530, #531, #533, #534):

• New: A GitHub access token saved in GitLane now covers pull requests too, not just fetch and push. The GitHub CLI still has to be installed, but it no longer needs to be signed in.
• Changed: Settings › Accounts shows one connection method at a time: the provider's CLI, an access token, or an SSH key. Each one says what it covers and where to get the credential. For an access token, you choose whether it's stored in GitLane's keychain or in your Git credential helper.
• Fixed: Pasting a GitHub personal access token now works. A credential save that fails tells you why, and when another credential helper is answering for the same host, GitLane says which username it returned and offers to forget it and save again.
• Fixed: After saving a token, GitLane checks it against the open repository's remotes. It no longer deletes a valid token just because that token can't read one repository.
• Fixed: A token typed with a mixed-case host (for example GitHub.com) is now found when Git asks for it. Tokens can no longer appear in credential error messages.

Appearance (#526):

• Changed: New installs follow your system's light or dark theme. If you've already picked a theme, it's kept.

Windows (#528):

• Fixed: Reset preview, discard all, and worktree cleanup no longer fail on Windows because of \\?\ long-path prefixes being passed to Git.

Good to know

Where the token lives decides what it covers. Kept in GitLane's keychain, a GitHub token answers fetch, pull, push and pull requests. Kept in your own credential helper, it's shared with Git in the terminal, and pull requests still go through a signed-in gh. A gh account bound to the repository always wins over the token.

Walkthrough: Use a GitHub token for pull requests.

Installers: Download GitLane.