ChatGPT. A Git workflow answers: how does code move from a developer’s machine to production, safely and predictably?
| Question the workflow answers | Why it matters |
|---|---|
| Where does new work start? | From main, develop, a fork, or a release branch? |
| Where does finished work go first? | Into main, develop, a staging branch, etc.? |
| Which branch represents production? | Usually main, master, or production. |
| When do we release? | Every merge, manually, on a schedule, or after stabilization. |
| How do we isolate unfinished work? | Feature branches, forks, release branches, feature flags. |
| How do we fix production bugs? | Hotfix branch, direct patch to main, or normal feature branch. |
| How do we mark versions? | Tags like v1.2.0, release branches, or deployment records. |
| How much review/control is required? | Direct commit, PR/MR, code review, CI checks. |
| How long do branches live? | Long Lived / Short Lived |
Feature Flag git github Review Merge Request Prompt Git Tag Versioning Strategies