gitte

Monorepo-like development across many git repositories — without the monorepo.

Gitte keeps all your repos in sync, runs startup checks to verify your local machine is ready, and executes ordered actions (build, up, down, …) across projects with dependency resolution and parallel execution.

---

Table of contents

• Features
• Installation
• Quick start
• Commands
• Configuration
• Environment variables
• Telemetry
• Global flags
• State and override files

---

Features

• Startup checks — verify tools, versions, and credentials before doing anything
• Git sync — clone and pull all configured repositories in parallel
• Ordered actions — run commands across projects with needs-based dependency ordering and parallel execution
• Project toggles — interactively enable/disable projects per machine
• Template inheritance — share action definitions across similar projects
• Feature gates — toggle environment-variable-based behaviours per machine
• Auto-discovery — discover and sync repositories from GitLab groups or GitHub orgs
• Clean operations — remove untracked files, reset local changes, or check out default branches across all repos
• TTY-aware output — animated spinner TUI in a terminal, structured plain-text output in CI / non-TTY

---

Installation

APT (Debian and Ubuntu)

curl -fsSL https://gitte-apt.cego.dk/gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/gitte.gpg
echo"deb [signed-by=/etc/apt/keyrings/gitte.gpg] https://gitte-apt.cego.dk ./"| sudo tee /etc/apt/sources.list.d/gitte.list
sudo apt update
sudo apt install gitte

Homebrew (macOS and Linux)

brew tap cego/gitte https://github.com/cego/gitte
brew install cego/gitte/gitte

Binary download

Download the latest binary from the releases page and place it on your PATH.

Go install

Requires Go 1.24 or later.

go install github.com/cego/gitte@latest

---

Quick start

1. Create a .gitte.yml in your workspace root:

startup:
git-present:
type: commandcmd: ["git", "--version"]hint: "git is not installed"projects:
myservice:
remote: git@github.com:example/myservice.gitdefault_branch: mainactions:
start:
groups:
local: ["docker", "compose", "up", "-d"]stop:
groups:
local: ["docker", "compose", "down"]

2. Run the full pipeline:

gitte run start local

Gitte will run startup checks, pull all repos, then execute the start action for group local across all enabled projects.

---

Commands

Overview

Command	Description
gitte run [action] [group] [projects]	Full pipeline: startup checks → git sync → actions
gitte actions [action] [group] [projects]	Run actions only (skip startup and git sync)
gitte startup	Run startup checks only
gitte gitops [--discover]	Clone/pull all repos; --discover also fetches from configured sources
gitte list	List all projects and their available actions
gitte toggle	Interactive TUI to enable/disable projects per machine
gitte clean <subcommand>	Clean up repos (see below)
gitte features list|enable|disable	Manage feature gates
gitte sources	Manage discovery sources (GitLab groups / GitHub orgs)
gitte token set|get|delete|list	Store API tokens in the system keyring
gitte validate	Validate config: schema, cycles, missing references

Argument syntax

Arguments to run and actions are positional: action [group] [projects].

gitte run start # start action, all groups, all enabled projects
gitte run start local# start action, group local, all enabled projects
gitte run start local myservice # start action, group local, project myservice only
gitte run start local frontend+backend # start action, group local, projects frontend and backend
gitte run start+test # run start then test, all groups, all enabled projects

Use * or all as a wildcard. Combine multiple values with +.

gitte clean

Destructive cleanup operations across all configured repositories. Each subcommand shows a live progress TUI while running.

gitte clean untracked # remove untracked files (git clean -fdx)
gitte clean local-changes # reset repos with local changes (prompts before acting)
gitte clean master # checkout the default branch in all repos
gitte clean all # run all three in sequence

gitte clean local-changes lists affected repos and prompts:

Reset [a]ll / [i]ndividually / [C]ancel?

---

Configuration

See docs/config.md for the full configuration reference.

---

Environment variables

Variable	Default	Description
GITTE_CWD	process cwd	Override the working directory
GITTE_NO_TTY	0	Set to 1 to force plain-text output (no TUI)
GITTE_NO_NEEDS	0	Set to 1 to ignore needs dependencies
GITTE_NO_REBASE	false	Set to true to skip auto-rebase onto default branch
GITTE_MAX_TASK_PARALLELIZATION	unlimited	Cap the number of concurrent tasks

---

Telemetry

Gitte can export OpenTelemetry traces to an OTLP/HTTP endpoint (e.g. Elastic APM) to help debug failures. Traces capture per-repo git context (branch, commit SHA, dirty state) and per-task outcomes with errors. To identify which developer and machine hit a failure, the OS username (user.name) and hostname (host.name) are attached to every trace.

What is recorded: the gitte CLI arguments and each action's command line are exported as span attributes (this is intentional — knowing what ran is the point). Note that gitte's injected environment — a project's env, env_when, and feature-gate env — is also exported on task spans (the gitte.env attribute) and in the task logs; the inherited process environment (everything in os.Environ) is not. So keep secrets out of action command definitions, CLI arguments, and config env/feature-gate blocks — pass real secrets through the process environment instead. Full remote URLs are never collected either (repos are identified by name only).

Each gitte run produces a structured trace: a root span with child spans for each phase (startup, gitops, actions), a span per startup check, a span per action (e.g. build, up) parenting its task spans, and a span per repo sync. Action and startup command output is also shipped as OTEL logs, correlated to the span that produced each line (stdout → INFO, stderr → WARN).

Logs are enabled with tracing; set GITTE_TELEMETRY_LOGS to off, false, or 0 to keep traces but disable the (higher-volume) log export. Keep secrets out of command output — log lines are exported verbatim.

Enable it via the shared config:

telemetry:
endpoint: https://apm.example.com:8200headers:
Authorization: "Bearer <secret-token>"# or: "ApiKey <base64-key>"

Environment variables:

Variable	Effect
GITTE_TELEMETRY=off, false, or 0	Disable telemetry locally (case-insensitive; surrounding whitespace is ignored)
GITTE_TELEMETRY_URL	Override the endpoint; whitespace is trimmed and https:// is added when no scheme is present
GITTE_TELEMETRY_LOGS=off, false, or 0	Disable OTEL log export (keep traces; case-insensitive with surrounding whitespace ignored)
OTEL_EXPORTER_OTLP_ENDPOINT / OTEL_EXPORTER_OTLP_HEADERS	Standard OTEL env vars; endpoint vars are used when no gitte endpoint is set, and headers can provide credentials for a GITTE_TELEMETRY_URL override

Precedence: GITTE_TELEMETRY=off|false|0 > GITTE_TELEMETRY_URL > config endpoint > OTEL_EXPORTER_OTLP_*. Telemetry is best-effort and never blocks or slows gitte; export failures are silently ignored. When GITTE_TELEMETRY_URL overrides the config endpoint, config headers are not used; set OTEL_EXPORTER_OTLP_HEADERS to provide override-endpoint credentials through the OTEL exporter.

---

Global flags

--config <path> Path to .gitte.yml (default: auto-detected by walking up)
--cwd <path> Override working directory
--no-tty Force plain-text output

---

State and override files

.gitte-state.yml — stores per-machine state: project toggles, feature gate overrides, and remote config cache. Gitte automatically adds this file to .gitignore. Do not commit it.

.gitte-override.yml — deep-merged on top of .gitte.yml when present. Use this for local machine-specific settings that should not be committed (e.g. sources added via gitte sources add).