Branches and environments
Work on changes with the right source, data, and running apps.
Use branches to develop and test changes within a project. Each branch combines a line of source code with the runtime context used to run its apps.
Branches
A project has a main branch. Additional branches let you work on changes separately. Creating a branch creates a Git branch from the chosen source branch, provisions its database, and copies the source branch's current app deployments.
Branch environments
The environment is the context in which your code runs: its database, app deployments, and configuration. In Continual today, that runtime context is tied to a branch.
Project settings supplies environment variables to the project's sandboxes. Use Project settings to manage these values, and check the branch when working with apps or data.
Work and preview on a branch
Threads run with project and branch context. Inspect the changes and try the app preview in that context before publishing an update.
The CLI uses the current Git branch in a linked project, or the branch supplied by a managed Continual execution. Its branch override lets you select a different target explicitly.
Database changes and data belong to the branch runtime. Do not assume that reviewing or merging source also transfers database changes or data between branches.
Publish apps
Apps are deployed in a project and branch. Publishing an app updates the deployment for that target; confirm the branch before publishing.