git-github-workflowlisted

# Git & GitHub Professional Workflow Stack-agnostic conventions for any software project. The goal: a commit history that reads like a changelog, branches that map one-to-one to units of work, a `main` branch that is always green and always deployable, and CI that catches regressions before review. ## Core principles - `main` is sacred. Always deployable, always green, never force-pushed. - One commit = one logical change, revertible in isolation without breaking anything. - One branch = one unit of work. Open small, review fast, merge, delete. - Rewrite local history freely. Never rewrite history others have pulled. --- ## Before you start any work ```bash git status # working tree clean? git branch --show-current # on the right branch? git fetch origin && git log HEAD..origin/main --oneline # behind main? ``` If the tree is dirty: commit, stash, or discard before starting unrelated work. If the branch is behind `main`: rebase first (see "Keeping a branch in sync"). --- ## Commits ### Format — Conventional Commits ``` type(scope): description [optional body] [optional footer] ``` - `type` required, one of: `feat`, `fix`, `chore`, `docs`, `test`, `refactor`, `style`, `perf`, `ci`. - `scope` optional. Include when the change is localized to a named area (`auth`, `api`, `parser`, `deps`). Omit when the scope adds no information. - `description` is imperative mood, lowercase, no trailing per