moai-ref-git-workflow

GitFlow uses separate branches for features, releases, and hotfixes for structured releases, GitHub Flow uses a simple main and feature branch model for continuous deployment, and Trunk-Based Development uses short-lived feature branches merged frequently to main for rapid integration.

To write conventional commits for a git workflow, use structured prefixes like feat, fix, or docs in your commit messages to communicate the intent of changes, maintain a clean project history, and standardize collaboration across software teams.

The best way to set up branch naming conventions for multi-repo environments is to apply standardized patterns across all repositories, ensuring uniform branching prefixes for features, bugfixes, and releases to guide engineers in consistent collaboration.

To create PR templates that improve code review quality, define standardized markdown files in your repositories that prompt contributors for essential information, enforce governance rules, and guide reviewers through the merge strategy process.

You should use Trunk-Based Development instead of GitFlow when your software team prioritizes rapid integration and continuous deployment over structured release cycles, applying short-lived branches to enforce safe and scalable development.

You need pull request templates to enforce governance rules in your git workflow because they standardize the review process, ensure merge strategy guidance is followed, and reduce integration friction across multiple repositories.