← Back to Help Center

1. 1. What Collaborate syncs

   Collaborate stores the shared project files: collab pull downloads the tip, collab push publishes your edits so other developers can pull them. Branches, pull requests, and merges resolve file conflicts between people.

2. 2. What deploy tools do

   Commands such as deploy --auto (L5 prepare-deployment) build and ship a tree to a production server. That flow is outside Collaborate. Deploy does not replace collab push — if you only deploy, teammates cannot download your changes from the repository.

3. 3. Recommended loop

   Dev A: pull → edit → push (feature branch). Dev B: pull → edit → push. Open a pull request, review, merge to main. Then run your org's deploy tool from the merged default-branch tip (or an agreed release).

4. 4. Protect main

   Turn on branch protection and require review to merge so production tracks reviewed Collaborate history — not unshared local-only trees.

5. 5. Before you deploy

   Confirm collab status is in sync on the branch you intend to ship, run your project lint/build locally (or CI when available), then deploy. Collaborate tip commit on the repo page is the source-of-truth marker for what was merged.