Git workflow & releases

Branches (typical)

Branch pattern	Deploy target	Trigger (summary)
develop	Dev	Push with src/ changes → Lambda via Terraform
release-v*	Stage	Push with src/ changes → stage Lambda
GitHub Release (tag from release branch)	Prod	Published/edited release → prod Lambda + static

Exact workflow files: .github/workflows/*.yaml.

Static-only changes

• Changes under static/ sync to S3 via develop-static, staging-static, and (for prod) the production workflow — no Lambda redeploy needed when only assets change.

Version branches

• release-vNNN branches track staged API versions; coordinate with release managers before cutting.

Hotfixes

• Follow team hotfix process — often branch from prod tag or release branch, then merge back to develop to avoid drift.

Local branches

• Feature branches merge to develop via PR; keep commits focused and lint-clean for faster review.

Related

• Infrastructure & CI/CD
• Security & secrets