Workflows and Conventions

Git 1,932 lets you branch any way you like, so every team needs a written rule: how long branches live, how they return to main, and what a commit message says. This section compares the three common workflows, picks one for BookNest, and makes its commit messages precise enough to write the release notes.

Subsections

• Trunk-Based Development
• GitHub Flow
• Git Flow
• Choosing a Workflow
• Conventional Commits
• Commit Message Templates
• Squash vs Preserve
• Linear History
• Release and Hotfix Branches