Module 1 · A shared project
- Put the project in version control
- Ignore generated folders
- Make a first commit with a clear message
- Confirm a second person can download it
COURSE
Version Control for Game Teams
$63.00
Use branches, locks, and reviews so a three-person team stops overwriting each other’s scenes.
About
Use branches, locks, and reviews so a three-person team stops overwriting each other’s scenes. Across about 7 hours you will put the project in version control, do feature work off the main branch, lock or coordinate binary files such as scenes, and write what the change is meant to do.
Beginner · 7 hours · Production
Curriculum
Module 2 · Branches
- Do feature work off the main branch
- Keep the main branch playable
- Name the branch for the task
- Merge only after a look from someone else
Module 3 · Conflicts
- Lock or coordinate binary files such as scenes
- Read a conflict instead of keeping both blindly
- Ask who owns the file
- Test the game after the merge
Module 4 · Reviews
- Write what the change is meant to do
- Review one other person's change
- Reject a commit that breaks the build
- Write the team rule in a short page
