Configuration

Git Config Settings

Setting	Values	Default	Description
`loom.remote-type`	`github`, `gitlab`, `azure`, `gerrit`, `plain`	Auto-detected	Override the remote type for `git loom push`
`loom.push-remote`	Any remote name	Auto-detected	Override which remote to push to (e.g., `personal` for fork workflows)
`loom.hideBranchPattern`	Any prefix string	`local-`	Prefix for branches hidden from `loom status` by default
`loom.pruneGoneBranches`	`true`, `false`	`false`	Let `git loom update` remove local branches whose remote branch is gone

`loom.remote-type`

By default, git loom push auto-detects the remote type:

GitHub — if the remote URL contains github.com
GitLab — if the remote URL contains gitlab
Azure DevOps — if the remote URL contains dev.azure.com
Gerrit — if .git/hooks/commit-msg contains “gerrit”, or you confirm the prompt when the remote looks like Gerrit
Plain Git — otherwise

You can override this with:

git config loom.remote-type github   # Force GitHub push (push + PR, stacked PRs)
git config loom.remote-type gitlab   # Force GitLab push (merge request push options)
git config loom.remote-type azure    # Force Azure DevOps push (push + open PR)
git config loom.remote-type gerrit   # Force Gerrit push (refs/for/<branch>)
git config loom.remote-type plain    # Force a plain force-with-lease push

By default, git loom push uses the integration branch’s remote for pushing. One exception: if the integration branch tracks a remote named upstream and a remote named origin also exists, pushes go to origin automatically (the standard GitHub fork convention).

For non-standard fork setups where your remotes have different names, set this explicitly:

git config loom.push-remote personal

For example, with remotes:

origin → upstream read-only repository
personal → your fork (where you push)

Now git loom push will push to personal regardless of remote names.

`loom.hideBranchPattern`

Branches whose names start with this prefix are hidden from loom status by default — both the branch section and its commits are suppressed. Pass --all to show them.

git config loom.hideBranchPattern "local-"   # default: hide local-* branches
git config loom.hideBranchPattern "secret-"  # hide secret-* branches instead
git config loom.hideBranchPattern ""         # disable hiding entirely

Hidden branches remain fully accessible to the other loom commands (fold, drop, commit, etc.), except push, which never publishes a hidden branch nor a branch stacked on one.

When creating or renaming a branch to a name that matches this prefix, git-loom prints a warning.

Environment Variables

Variable	Description
`NO_COLOR`	Disable colored output when set (follows the NO_COLOR standard)
`TERM`	Colors are automatically disabled when `TERM=dumb`

CLI Flags

Flag	Description
`--no-color`	Disable colored output
`--theme <auto\|dark\|light>`	Set the graph color theme (default: `auto`)

`--theme`

Controls the color palette used for graph output.

Value	Behavior
`auto`	Detect the terminal background and choose dark or light automatically. Falls back to dark if detection fails or output is not a TTY.
`dark`	Always use the dark theme (optimized for dark terminal backgrounds).
`light`	Always use the light theme (optimized for light terminal backgrounds).

git loom --theme light
git loom --theme dark status

Keyboard shortcuts

git-loom