Home › Per Git docs, REBASE vs MERGE for integrating fe…
Per Git docs, REBASE vs MERGE for integrating feature branches differs in which property of the history?
ARebase keeps all old commits; merge deletes them entirely
BRebase merges binaries; merge only touches code files
CRebase produces linear history; merge preserves graph topology
DRebase requires Git LFS while merge does not need it
Answer & Solution
Correct answer: C. Rebase produces linear history; merge preserves graph topology
Pro Git Ch. 3.6 Rebasing: rebase replays commits on a new base (linear); merge adds a merge commit (preserves the branch shape).
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 In 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 Pro Git on workflows, the GIT-FLOW model uses long-lived branches for which purposes?Per Perforce Helix docs, EXCLUSIVE checkout (file locking) is commonly used in game studio