Contributing

Branching & PR Workflow

main ─────────────────────────────────────●── (stable releases)
                                         /
dev ──●────●────●────●────●────●────●───● ── (integration branch)
       \       / \       /
        \     /   \     /
feat/x   ●──●     ●──●   feat/y

Steps

1. Create a branch off dev

   git checkout dev
   git pull
   git checkout -b feat/my-feature
   

2. Make your changes, commit often

   git add -A
   git commit -m "feat: add X"
   

3. Push and open a PR → dev

   git push -u origin feat/my-feature
   

   Then open a PR targeting dev (not main).

4. Owner reviews and merges to dev

5. Periodically, dev is merged to main (release)

Branch Naming

Prefix	Use for
feat/	New features
fix/	Bug fixes
docs/	Documentation only
infra/	CDK / infrastructure
data/	Dataset updates

Commit Messages

Use Conventional Commits:

feat: add Neptune batch writer
fix: handle empty OBO files
docs: update data explorer page
infra: add S3 browser to ECS

Or Just File an Issue

If you don't want to write code, open an issue describing what you need. Tag it with enhancement, bug, or question.