Git Overview

Vegha workspaces are folders on disk and collections are plain-text .bru files, which makes them a natural fit for version control. Vegha includes a built-in git UI so you can manage history without leaving the app.

Why .bru and git work well together

Because every request, environment, and collection is a plain-text file, your API project behaves like source code:

Changes produce readable, line-level diffs
Branches and merges work the same way they do for code
Pull requests can review API changes alongside application changes

The native git UI

Vegha’s git support is built on LibGit2Sharp — no external git binary is required. Everything runs in-process and works the same across platforms.

The Source Control panel is where you stage changes, write commits, and run remote operations. Supported operations include:

Operation	Purpose
init	Start tracking the current workspace
clone	Copy a remote repository into a new workspace
branch / checkout	Create and switch branches
stage / commit	Record changes to history
push / pull / fetch	Sync with a remote
stash	Set aside uncommitted work
diff	Inspect changes line by line
merge	Combine branches, with a conflict resolver

Init vs clone

Init turns an existing workspace folder into a git repository — use this when you already have collections locally.
Clone creates a workspace from an existing remote repository — use this when collections already live in git.

Credentials

Vegha authenticates to remotes two ways, with credentials stored in the OS keystore:

HTTPS with a personal access token (PAT)
SSH with a key pair

What to .gitignore

Commit your .bru collections — that is the point. But keep machine-specific and sensitive data out of history:

Local secret values and credentials
Editor or OS scratch files

Continue with committing, pushing, and pulling and branches and merging.