Git Workflow

Branches

Branch	Purpose
main	Always deployable
feat/xxx	Features
fix/xxx	Bug fixes
docs/xxx	Documentation only
refactor/xxx	No behavior change

Commits

Use Conventional Commits. Keep them short.

Format

type(scope): description

Examples

feat(core): add galaxy type definitions
fix(ui): correct axis scale on scatter plot
docs: add data sources to handbook
refactor(viz): extract d3 bindings
chore: update dependencies

Types

• feat — New feature
• fix — Bug fix
• docs — Documentation only
• refactor — Code change that doesn’t fix bug or add feature
• test — Adding or fixing tests
• chore — Maintenance tasks

Rules

• Present tense (“add” not “added”)
• Lowercase
• No period at end
• Body only if necessary
• Keep under 72 characters

Pull Requests

Title

Follow commit format:

feat(core): add coordinate transforms

Description Template

## What
[One sentence describing what this PR does]

## Why
[Optional if obvious from the issue]

## Notes
[Optional implementation details or decisions]

Checklist

Before requesting review:

• Tests pass (pnpm nx affected -t test)
• Lint clean (pnpm nx affected -t lint)
• Types complete (no any)
• Commits are clean (rebase if needed)

History Management

Rebase Before Merge

git fetch origin
git rebase origin/main

Squash Only If Messy

If your commits tell a clear story, keep them. If they’re “fix typo” and “oops”, squash.

Each Commit Builds

Every commit in history should:

• Build successfully
• Pass tests
• Be meaningful on its own

No “Fix Typo” Commits

Amend instead:

git add .
git commit --amend --no-edit