Version Control Workflow

Method

A production method for managing project files, code, assets, changes, and releases across a team.

Description

Version control workflow helps a team work on the same project without losing work or overwriting important changes. In immersive production, it may cover code, Unity or Unreal projects, assets, builds, documentation, and release versions. A good workflow makes it clear what changed, who changed it, and which version should be used.

Typical Use

Used in software development, real-time production, technical art, asset pipelines, build management, documentation, and multi-person teams.

Scope Note

This method may include branching rules, commit habits, file-locking rules, version names, release tags, backup practices, review steps, and rollback plans.

Boundary Note

The workflow should fit the team’s skill level and project risk. A complex system that no one follows can be worse than a simple one used consistently.

Collaboration Note

Usually involves developers, technical artists, producers, 3D artists, designers, QA testers, and anyone who edits shared project files.

Related entries