Version control checklist for adding an outside team to a live game project
Co-development handoffs often fail over version control, because game projects rely heavily on binary files that cannot be merged when two people edit them at once. Time-zone gaps between studios make informal coordination unreliable, so the rules need to be enforced by tooling. The article recommends locking binary asset types such as Unity scenes, Unreal map and asset files, and source art, while leaving text files mergeable, using Perforce exclusive-open typemaps or Git LFS lockable patterns. Etiquette matters as well: teams should release locks before logging off, state their reasons, and have a clear policy for breaking stale locks. Dividing project files by ownership, through sub-levels, separate folders, and permissioned streams, reduces collisions further.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
Discussion (0)
Log in to join the discussion and vote.
Log in