Home › Per Pro Git on workflows, the GIT-FLOW model use…
Per Pro Git on workflows, the GIT-FLOW model uses long-lived branches for which purposes?
Amain, develop, feature/release/hotfix branches
Bfeature branches that never merge back to main
Ctags only on the main branch with no branches
Dmain only with all work direct on main branch
Answer & Solution
Correct answer: A. main, develop, feature/release/hotfix branches
Vincent Driessen 2010 'A successful Git branching model' (linked from Pro Git): main = production; develop = next release; feature/release/hotfix branches around them.
Related questions
In commercial game studios using Perforce, the STREAMS feature serves a role similar to whPer Pro Git + Git LFS docs, when migrating an existing repo with large binaries to LFS, thIn modern game CI, an ARTEFACT CACHE (Bazel / SCons / Unreal DDC) accelerates rebuilds by Per Git docs, REBASE vs MERGE for integrating feature branches differs in which property oIn a deterministic build pipeline, BUILDS for the same git commit should produce which proPer Unity Asset Bundle docs (and Unreal Pak files), splitting assets into smaller packagesIn a typical game build pipeline (e.g. Unity Cloud Build, Jenkins), CI is used primarily tPer Perforce Helix docs, EXCLUSIVE checkout (file locking) is commonly used in game studio