Skip to main content

Collaborate with version management

Team convention​

  • One long-lived branch is the standard version.
  • Each customer has exactly one long-lived customer/* customer version.
  • Normal members use Save changes, Sync team, Update standard, Publish standard, and Mark delivery.
  • Repository owners use Advanced Git only for conflicts, reviews, or unusual repairs.
  • Published release and delivery markers are never moved or reused.

Theseus is hosting-provider independent. GitHub, GitLab, Azure Repos, Qixin Cloud Code, and self-hosted Git can all be the team remote.

Initial setup​

  1. Create the remote repository and team permissions.
  2. Open Versions in the editor and initialize the repository; the current branch immediately becomes the standard version.
  3. Configure team sync, save the shared equipment project, and sync it.

Develop shared features​

  1. Select Standard version and choose Sync team.
  2. Change shared control logic, pages, objects, or defaults.
  3. Add a short optional note and choose Save changes.
  4. Build, simulate, and validate standard machine behavior.
  5. Choose Sync team; use Publish standard when it is ready for customer work.

Develop a customer project​

  1. Choose New customer version and enter only the customer name and code.
  2. Save options, protocols, site parameters, and customer-specific flow on that version.
  3. Choose Sync team.
  4. When shared features change, choose Update standard from the customer version.
  5. Build again and regression-test customer-specific behavior.

A conflict aborts without leaving a partial merge. Someone who understands both the standard machine and the customer site should resolve it in Advanced Git. Do not work around it by copying the project or creating another customer branch.

Site delivery​

  1. Confirm the selected customer version, site, and target equipment.
  2. Save changes and sync the team.
  3. Accept the controller, I/O, communications, safety, HMI, and operating flow.
  4. Choose Mark delivery and enter the site, version, and note.
  5. Confirm team sync completed. If offline, use Sync team after connectivity returns.

Required human checks​

  • The selected customer, site, and version are correct.
  • Shared files contain no credentials, production data, or temporary machine files that should remain private.
  • Updating the standard did not overwrite customer options or actions.
  • The release or delivery marker matches the actual Build installed on the machine.