Version management reference

The editor's Versions panel uses automation-project language by default. Commissioning, delivery, and controls engineers do not need to understand Stage, Commit, Pull, or Push. The workspace remains a standard Git repository, and experienced users can open Advanced Git.

New Apps do not create a repository automatically. Select Initialize repository in the Versions panel the first time version control is needed; Theseus immediately uses Git's current branch as the standard version without another confirmation step. Theseus uses Git installed on the computer; if Git is not found, the panel provides Git for Windows download and recheck actions without affecting App files, editing, or Build.

Two version types

• Standard version contains shared machine logic, common pages, standard I/O, and default configuration. Any Git branch may serve this role; it need not be named main.
• Customer version is one long-lived branch per customer. Theseus generates customer/<customer-code>-<customer-name> and keeps options, site parameters, protocol differences, and custom actions there.

Normal users do not create change/*, hotfix/*, or release branches. Repository owners use Advanced Git for temporary branches, fine-grained commits, and unusual repairs.

Default actions

The selector lists only the standard version and customer/* versions. Switching is disabled while edits are unsaved.

A newly initialized repository uses its current branch as the standard version. An imported repository prefers the remote's declared default branch. Only an older repository without a remote default, or one with a stale standard-version setting, asks for manual confirmation.

Action	Result
Save changes	Include all current edits and save one local version; the note is optional
Sync team	Fetch team work, integrate it deterministically, then upload the current version and markers
Update standard	Fetch the latest remote standard and merge it into the current customer version
Publish standard	Mark a standard release and sync it
Mark delivery	Record the site, version, and note on a customer version and sync it

Save changes works offline. The panel shows that team sync is pending until Sync team succeeds.

Create a customer version

1. Open or set the standard version.
2. Choose New customer version from the selector.
3. Enter the customer name and code.
4. Choose Create and open.

Theseus always starts it from the standard and checks it out. It does not ask for a branch name, start point, or checkout option. Continue using the same customer version for later deliveries.

Sync and conflicts

Sync requires a saved workspace. Remote-only changes fast-forward. When both sides changed, Theseus keeps an explicit merge record. A conflict aborts and restores the pre-operation state; Theseus does not auto-stash, swallow the error, or guess customer configuration.

Update standard fetches before merging the remote standard, so it cannot silently use a stale local standard. Engineers who understand both the common machine and customer site should resolve conflicts in Advanced Git.

Releases and delivery traceability

• Standard releases use immutable annotated release/vX.Y.Z tags.
• Site deliveries use immutable annotated delivery/<customer>/<site>/<version> tags.
• All edits must be saved first. Markers sync automatically; after a network failure they remain safe locally and are shown as pending sync.
• Create a new marker for a correction; never move or reuse a published marker.

Advanced Git

Advanced Git retains Changes, Branches, History, Stage, Unstage, Commit, Fetch, Pull, Push, comparisons, arbitrary branch creation, and remote configuration. Returning to Simple mode does not change repository state.

Credentials use the system credential helper/GCM or SSH agent. Update an HTTPS token from the authentication prompt and never embed credentials in a remote URL or App file. Version management is desktop-only.

Delivery checklist

• The correct customer version is selected.
• Changes are saved and team sync has completed.
• After updating the standard, Build and regression checks cover I/O, communications, safety, pages, and control flow.
• The delivery marker matches the version installed on the machine.