Git Module
A full Git client lives inside Tigrister. You can initialize repositories, stage and commit changes, branch, merge, stash, push, pull, and resolve conflicts — without opening a terminal or installing an IDE plugin. Everything ships in the app.
Where It Is Available
The Git client is wired into two places: the Flow Runner sidebar (one repository per flow group) and the Load Test sidebar (one repository per spec group). Both entry points open the same Git panel — the only thing that changes is which folder the repository lives in.
- •Flow groups: the panel opens at flows/<group-name>. Flows, environments, lifecycle scripts, and assertions inside that group are versioned together.
- •Load test spec groups: the panel opens at load-tests/<group-name>. Specs, steps, thresholds, per-test-type configurations, and lifecycle scripts are versioned together.
- •Nowhere else: the Git panel only accepts these two scopes. Other areas of Tigrister (Box, Projects, OpenAPI, History) are not tracked by this module.
The Per-Group Repository Model
Each flow group and each spec group is its own independent Git repository. A single workspace can hold many small, focused repositories — one per API surface, one per project, one per team — instead of a single mega-repository for everything.
- •Isolation: a commit in one group never touches another. Branching, merging, and rebasing happen inside that group's repository only.
- •One remote per group: each repository can be connected to its own remote. Put one flow group on GitHub, another on an internal GitLab, a third on Gitea — all in the same workspace, all driven from the same Git panel.
- •Independent history: every group has its own branches, its own commit log, and its own stashes. There is no shared parent repository tying them together.
Privacy by Design
The Git panel never commits secrets. Authentication credentials, OS secrets, Vault values, and per-host access tokens are deliberately kept out of the tracked files — only their key names and references are versioned. Access tokens used to talk to remotes live in the operating system's keychain and are never written to the repository. The dedicated What is Not Versioned sub-section at the end of this chapter lists every excluded category.
What This Chapter Covers
The sub-sections below walk through every screen and workflow exposed by the Git panel — from the first moment you open it on an empty folder, through daily commit-and-push work, all the way to branch comparison, conflict resolution, and the safety rails that stop you from losing work.
- •Getting in: Opening the Panel, Setup Wizard.
- •Daily work: The Toolbar, Overview, Changes, Commit Mode.
- •Going deeper: History, Branches, Branch Compare, Stashes, Merge & Conflict Resolution.
- •Configuration and guardrails: Settings, Safety Rails, What is Not Versioned, Best Practices.