Revisions and Version Control
Version control works at two levels: revisions track how one Resource changes, and branches track which Resources belong together in a System.
Revisions
A revision is one version of a Resource. The Resource ID never changes, and each revision gets its own Revision ID, so you can point at the exact data. Revisions can't be changed, and earlier revisions are kept, so there's no need for copies named FINAL or FINAL_v2.
A new revision is created when:
- You upload a new file as a version of the Resource
- You connect the updated source of a connected Resource
- Some update functions save their result as a new revision of the model, such as Teamwork Cloud tag updates
- A partner updates a Resource shared with you over a Secure Connection
To create a new revision, add the new version on the Resource itself. Uploading the file again from the Resources view or a System creates a separate Resource, not a new revision.
Compare revisions
When a Resource has two or more revisions and its format supports comparison, the Compare tab shows what changed:
- Text, images, and other non-3D formats show a diff.
- 3D models show a 3D visual diff when both revisions are in the same format: OBJ, STL, GLB, glTF, 3MF, or MSH.
Branches
A branch is a named line of work on a System. It records which Resources and Subsystems belong together, and at which revisions. Every System starts with a baseline branch.
- Create a branch to work on a change without affecting baseline.
- Add revisions and save each change as a commit on the branch.
- Open a change request to review the differences and merge the branch into baseline.
The commit history shows who changed the System, when, and what it looked like at each point.