foundation-git-workflow

A Git branching strategy defines how your team creates, names, and merges branches to enable parallel work and continuous deployment. GitHub Flow uses feature branches with pull requests for review; Trunk-Based Development keeps most work on main with short-lived branches. Choose based on your deployment frequency and team size.

Conventional commits follow a structured format (type: description) for commit messages, enabling automated changelog generation and clearer history. They standardize how teams document changes, making it easier to understand what changed and why across your repository.

Interactive rebase lets you reorder, squash, or edit commits before merging to main, creating a linear, readable history. This removes intermediate debugging commits and organizes related changes logically, improving code review clarity and rollback precision.

A PR template standardizes what reviewers see: a summary of changes, the problem solved, testing approach, and links to related issues. This reduces review time, ensures quality gates are checked, and aligns the team on expectations for size, scope, and documentation.

Yes, CI/CD checks integrated into pull requests automatically run tests, linters, and security scans before merge. This enforces quality gates, prevents broken code from reaching main, and gives teams confidence in deployment readiness.