​

Deployment Workflow

Terra now uses a mainline release model: main is the source of truth, CI gates every change, and tags create human-readable GitHub releases.

​

Branch and Environment Model

​

Required CI Gates

1. Build/typecheck
2. ESLint
3. Vitest suite
4. No skipped Terra Playwright directives (check-terra-skipped-tests.mjs)
5. Chromium public status smoke test

​

Daily Development Flow

# Start from main
git checkout main
git pull origin main

# Create a short-lived feature branch
git checkout -b codex/my-change

# Work, commit, push
git add .
git commit -m "feat: ..."
git push -u origin codex/my-change

# Open PR to main
gh pr create --base main

​

Release Process (GitHub Releases)

​

Option A: Tag push (most direct)

git checkout main
git pull origin main
git tag v2026.2.22
git push origin v2026.2.22

git tag v2026.2.22.1
git push origin v2026.2.22.1

​

Option B: Manual workflow dispatch

• tag (optional; auto-generates vYYYY.M.D if omitted) If vYYYY.M.D already exists, the workflow auto-selects vYYYY.M.D.1, .2, etc.
• target (defaults to main)
• prerelease (optional)

​

Rollback

# Revert on main
git checkout main
git pull origin main
git revert <bad_commit_sha>
git push origin main

​

Quick Commands