Module 5 · Lecture 5.3
Team Workflow: Branches & Git
Why Creators work on branches, the Pull, Change, Validate, Push loop, and connecting your own Git repository.
Every change so far has happened on a draft branch. This lecture explains why that habit matters as soon as several Creators share one Knowledge Graph, and it walks the full loop of Pull, Change, Validate, Push.
You also watch a real merge conflict get resolved by hand, plus a walkthrough of how the same workflow extends to your own Git repository when your team prefers to review changes there.
Key points
- Two reasons for a branch: collaboration between Creators, and validating a substantial change before users see it.
- Business users on Main keep a seamless experience while you work.
- The loop is Pull, Change, Validate, then pull again and Push. The second pull catches what others changed in the meantime.
- A branch is created from the sidebar or from Git operations, and it starts as an exact replica of Main.
- The edit history lists every change and how far your branch is ahead of Main.
- A push pulls Main first, and conflicting edits open a merge editor where you resolve each one yourself.
- Git remote: connect your own repository so review and merging happen there, then Veezoo pulls the result back.
Check your understanding
Why create a development branch?
Branches let several Creators work without overwriting each other and let you validate a big change while Main keeps serving users.
You push your branch, but Main changed on the same lines in the meantime. What happens?
A push pulls Main first, and any conflict goes to a merge editor where you decide which version to keep.
Your team connects Veezoo to its own Git repository. What changes?
With a Git remote the review and merge happen in the repository, and Veezoo pulls the reviewed result back.