Source Control

Boltise has a full Git panel, so version-controlling a server does not mean alt-tabbing to a terminal. Open it with Ctrl+Shift+G, or from the sidebar.

It drives the real git binary on your machine, so anything Boltise does is visible to every other Git tool you use, and vice versa.

Committing

The panel splits your working tree into Staged Changes, Changes and Untracked. Stage what you want, write a message, and commit.

Stage, commit and push are separate actions. Add Remote links an existing repository; it does not create a repository, commit changes or push them.

Click a changed file to open a side-by-side diff in the editor. Staged changes compare HEAD with the index; unstaged changes compare the index with disk. It is the same Monaco view you write code in, not a plain-text dump.

Branches, tags and stashes

From the same panel:

Create, switch, filter and delete branches
Create, push and delete tags
Stash work in progress, then apply, pop or drop it

Deleting anything is a two-step click — the button asks you to click again to confirm, so a misclick on Delete branch costs nothing.

History

The panel renders a commit graph, so branches and merges are visible as shape rather than as a flat list. You can view any commit’s diff, see the history of one file, and blame individual lines to find when a line arrived and why.

Remote operations

Push, pull, fetch and clone all work, including against private repositories.

When Git needs credentials, Boltise catches the prompt and shows it as a dialog instead of letting Git hang waiting for a terminal that is not there. Credentials you choose to save are encrypted with Electron’s safeStorage when a secure OS backend is available. Boltise does not save them when secure storage is unavailable. SSH key passphrases are not saved by Boltise. Forget Boltise Git credentials clears Boltise’s saved credentials; it does not sign out an external credential helper or clear an SSH agent.

GitHub and enterprise hosts

Use the repository’s HTTPS or SSH clone URL, including the hostname supplied by your company. Repository links preserve that hostname. Unknown private hosts are not automatically classified as GitHub. SSH transport ports are not assumed to be web ports.

Choose Clone from GitHub on the dashboard or the GitHub icon beside Refresh in the Source Control header. Connect with a personal access token from your GitHub.com account. Token permissions expands the required permissions.

Remembered accounts use encrypted OS storage. When secure storage is unavailable, the connection lasts for the session only. Disconnect removes the Boltise connection and cancels its pending requests. It does not revoke the token on GitHub or remove external Git credentials. Disconnect to connect another account. OAuth/device login is not provided.

The repository picker lists repositories accessible to the token, 50 at a time. Search loaded repositories filters the pages already loaded; choose Load more repositories to include more. Fine-grained tokens need access to the selected repositories, Metadata read, and Contents read for cloning. Classic tokens need repo for private repositories. Partial organization access and permission, expired-token and rate-limit errors are shown explicitly.

Select a repository, a new folder name and project game, then choose its parent folder in the native picker. Boltise clones over HTTPS into an exclusive new folder and opens it as a project. Existing folders are refused. A cancelled or failed clone may leave a partial folder; inspect it before retrying. If cloning succeeds but opening fails, Open cloned project retries project opening. The account token is scoped to that clone’s exact host and repository path, without writing it into the clone URL or Git configuration. Subsequent Git operations use the regular Git credential-helper/askpass flow described above. Create repositories and manage pull requests on your Git host; these operations are not provided by the picker.

Private repositories require access for the account Git authenticates as. For GitHub HTTPS, use a personal access token with the repository permissions needed for the operation. Organizations may require token approval or SSO authorization; an account’s browser login alone does not authorize Git. See GitHub’s SSO authentication guidance.

API requests use Electron networking; clone and other Git operations use installed Git and SSH. Company VPN, proxy and trusted certificates must work with both. Keep TLS verification enabled. Branch protection, required reviews, and organization policies are enforced by the server; a rejected push is not a successful sync. Credential dialogs can be cancelled; network Git operations have a two-minute timeout. The GitHub picker has a Cancel request button; other Git operations do not have a general in-flight cancel button.

Working with a server repo

A FiveM server-data folder is not an obvious Git repository, and the useful convention is to be selective. Worth committing: server.cfg, your own resources, and BOLTISE.md. Worth ignoring: the FXServer build itself, cache/, logs, and anything containing your license key.

If your server.cfg holds sv_licenseKey directly, keep it out of the repository — put the key in a separate .cfg that is git-ignored and exec it.

Docs privacy