Set up a branching strategy

Design a Git branching strategy for an engineering team of [N] developers who release [Frequency, e.g. multiple times per day or weekly]. Compare Git Flow, GitHub Flow, and trunk-based development, evaluating each against your team's release cadence, CI/CD maturity, and need for parallel release trains. Recommend the best fit and define: branch naming conventions for feature, bugfix, hotfix, and release branches, branch protection rules and required status checks for main, a release tagging convention following Semantic Versioning, and the process for handling emergency hotfixes to production.