mint-commit

To enforce a standard git commit and promotion workflow, you mandate feature/* and hotfix/* branching patterns, require conventional commit messages with Co-Authored-By, and use squash merges for feature→dev and merge commits for dev→staging and staging→main. This prevents diverging histories and unsafe repository changes.

The correct branch flow forbids direct pushes to staging or main. It uses squash merges for feature→dev promotion PRs and merge commits for dev→staging and staging→main flows to preserve commit SHAs and ensure an auditable promotion history.

Yes, you need to run project test suites until they pass before committing changes. Pre-commit test verification is required to ensure no broken releases occur, and conventional commit messages with scopes and Co-Authored-By attribution must be used.

No, force pushes are explicitly forbidden when managing feature and hotfix branches. The standardized git commit workflow prescribes specific merge strategies and branch naming conventions to maintain an auditable and safe repository history.

Yes, this standardized commit workflow requires both git and the GitHub CLI. These tools are necessary to enforce branch naming conventions, execute pre-commit test verification, and create promotion PRs across dev, staging, and main.

The best way to prevent broken releases and diverging histories is to enforce a consistent git commit workflow with conventional commit messages, pre-commit test verification, no force pushes, and prescribed merge strategies like squash merges for feature branches.