Gitfox
🌙

Service Accounts and Jira Cloud

Service accounts let Gitfox authenticate HTTPS remotes and work with hosted repositories from the repository manager.

Gitfox supports accounts for:

  • GitHub
  • GitLab
  • GitLab Self-Managed
  • Bitbucket
  • Gitea

Open Gitfox → Settings → Accounts & Credentials, click Add Account, choose a provider, then choose the authentication method shown for that provider.

Authentication methods

GitHub, GitLab, and Bitbucket support OAuth and personal access tokens.

GitLab Self-Managed and Gitea support personal access tokens. They also require a Base URL because Gitfox needs to know which server to contact.

Bitbucket labels its token field as API Token. The other providers label it as Personal Access Token.

What service accounts are used for

Service accounts are used for HTTPS authentication and hosted-service actions such as listing and cloning repositories.

Select a GitHub, GitLab, GitLab Self-Managed, or Gitea account under Service Accounts in Repository → Configure Issue Sources… to use issue autocomplete for the preferred Git remote. The account must match the remote’s hosting service and server and have access to the repository. Bitbucket issue search is not supported.

The picker defaults to None. Saving an account in Settings does not automatically select it for a repository. Choose Add account… to open account settings, then return to the dialog and select the account after adding it. The selection is saved for each repository, and only the selected account is searched.

Issue search also works for SSH remotes and is independent of Git authentication.

Service accounts do not authenticate SSH operations. SSH remotes use your normal SSH configuration and keychain setup.

Jira Cloud

Gitfox also supports Jira Cloud accounts for issue autocomplete. These accounts search Jira issues; they are not used to list or clone Git repositories or authenticate Git remotes.

  1. Open Gitfox → Settings → Accounts & Credentials, then choose Add Account → Jira Cloud.
  2. Enter an Account Name to help identify the account.
  3. Set Site URL to your Jira site’s HTTPS address, such as https://your-team.atlassian.net.
  4. Enter the Email for your Atlassian account.
  5. Create an API token without scopes in Atlassian’s API token settings, then paste it into API Token. Gitfox’s Jira Cloud connection requires this token type. See Atlassian’s token instructions for help creating one.
  6. Click Add. Gitfox verifies the account before saving it.
  7. Open Repository → Configure Issue Sources… in your repository and select the account from the Issue Accounts section of the Issue tracker picker. Saving the account in Settings does not select it automatically.

Your Atlassian account must have access to the issues you want to search. If the token expires or is revoked, use the account’s error control in Settings to reauthorize it with a new token.

You can now use /i in the commit message editor to search for and insert Jira issue references. With a Jira Cloud account selected, only that account’s Jira issues are searched.

Generic HTTPS credentials

If a remote uses basic HTTPS authentication instead of a hosted-service account, add an HTTP/S Credential from Settings → Accounts & Credentials. Gitfox stores a display name, username, and password for that credential.