​

Branches

A branch is an independent release channel for a game. Each branch can point players to a different sequence of published versions.

​

Common branch strategies

Private branch availability depends on your active plan and permissions.

​

Design recommendations

• Keep one clearly identified production branch.
• Avoid creating branches without a defined audience.
• Use predictable names such as stable, beta, or qa.
• Restrict private branches to the users who need access.
• Do not use a branch as a substitute for versioning.

​

Publishing to a branch

When uploading through the interactive CLI, choose the destination branch carefully. The selected branch determines which players can receive the release.

​

Branch permissions

Access can be influenced by:

• Workspace membership.
• User or player permissions.
• Branch visibility.
• Plan capabilities.
• Launcher and game configuration.

Use the CLI permission option or the dashboard controls available in your workspace to review access.