Design a Simple Git Branching Strategy

Git & GitHub

Technical Specification

Define a branching strategy using main, develop (optional), and feature/* branches, and document rules for where to commit and how to merge.

Input/Output Samples

Input:team onboarding

Output:they follow clear branching rules

Optimal Logic Path

# CONTRIBUTING.md (example snippet)
- main: always deployable, protected branch
- feature/*: new features (e.g. feature/add-navbar)
- fix/*: bug fixes (e.g. fix/login-crash)
- Create PR from feature/* into main; require at least 1 review.

Architectural Deep-Dive

A clear branching strategy avoids chaos and ensures everyone knows where to put their work.