Gitfox
🌙

Commit Message Autocomplete

Gitfox can suggest file paths, commit hashes, emoji, and issue references while you write a commit message.

Open the commit window, then type / at the start of a line or after a space to see the available commands. You can also type a command directly, followed by a search term like this /gbug.

Autocomplete commands

Command Example Inserts
/f /f README A file path relative to the repository root
/c /c fix or /c a1b2c3d An abbreviated commit hash
/g /g bug or /g sparkles A Gitmoji emoji
/i /i login or /i 123 An issue reference such as #123 or PROJ-123

Use ↑ and ↓ to select a suggestion, then press Return or Tab to insert it. You can also click a suggestion. Press Esc to dismiss the list.

Choosing a suggestion replaces the slash command and its search text. For example, choosing the bug emoji for Fix /g bug produces Fix 🐛.

File searches match filenames and paths. Commit searches match commit subjects or hash prefixes. Gitmoji searches match emoji, shortcodes, or descriptions. Type a command without a search term to browse suggestions.

Choose issue sources

Issue autocomplete searches one selected account for the current repository. Open Repository → Configure Issue Sources…, or click Configure Issue Sources… below the /i suggestions.

The Issue tracker picker defaults to None. Saving an account in Settings does not automatically select it for a repository. Choose an account from one of these sections, which appear when you have matching accounts saved:

  • Service Accounts: select a GitHub, GitLab, GitLab Self-Managed, or Gitea account to search issues from the preferred Git remote. The account must match the remote’s hosting service and server and have access to the repository. This also works for SSH remotes, independently of the credentials used for Git authentication. Bitbucket issue search is not supported.
  • Issue Accounts: select a Jira Cloud account to search Jira issues that account can access.

Choose Add account… to open account settings and follow the service account or Jira Cloud setup steps. After adding the account, return to this dialog and select it.

The preferred remote is the current branch’s upstream remote when configured, otherwise origin, otherwise the first available remote. Only the selected account is searched, and the selection is saved for each repository. Choose None to turn off issue suggestions for that repository.

Type /i to browse recent issues, including open and closed issues, or add a title, number, or Jira key to narrow the search. Selecting an issue inserts its reference, such as #123 for a Git-hosted issue or PROJ-123 for Jira.

To turn references in commit messages into clickable URLs, use Commit Message Links.

If suggestions are missing

  • If the command list does not open, check that / is at the start of a line or follows a space.
  • For issue suggestions, explicitly select a service or Jira Cloud account in Configure Issue Sources…, even if it is already saved in Settings. With None selected, no issues are searched. Git-hosted issues also need a supported preferred remote that matches the selected account’s hosting service and server.
  • Check that your account can access the issues and that you have an internet connection. If Settings shows an account error, reauthorize the account. Jira requires an API token without scopes; replace it if it has expired or been revoked.
  • Try a shorter search or enter the issue number or key. For Jira summary searches, try the start of a word. Suggestions are limited, so an issue missing from the initial list may appear after you narrow the search.