# Git Workflow & Release Management This document defines the recommended Git workflow and release process for the Headlamp Sealed Secrets plugin. ## Overview The workflow implements a simplified Git Flow strategy optimized for Headlamp plugins: - **Development**: All active development on `main` branch - **Releases**: Tagged on `main`, published from tags - **Hotfixes**: Emergency fixes committed to `main` with patch version bumps - **Feature Branches**: Optional for large features (cleanup after merge) ## Branching Strategy ### Main Branch (`main`) - Single integration branch for all development - Protected: requires PR review before merge - All commits must pass CI checks - Always releasable ### Feature/Fix Branches (Optional) - Naming: `feature/description`, `fix/description`, `docs/description`, `chore/description` - Created from: `main` - Merged back to: `main` via PR - Deleted after: merge to main ### Release Tags - Format: `v..` (semantic versioning) - Created from: `main` branch (latest commit) - Example: `v0.2.4`, `v0.3.0` - Never force-push or delete release tags ## Commit Convention ### Format ``` ():