Development flow
Save changes
When you make changes to the data model, you can save them by clicking the “Save all” button in the actions bar at the top of the screen.Commit, merge or publish changes
After saving changes, click the button in the actions bar or in the Changes view. Its label says what it does by default:- Commit commits the changes to the branch you’re working on. It’s the default unless one of the cases below applies. The menu next to the button shows that branch’s name under Commit.
- Merge into … merges a shared branch into the branch it was created from. It’s the default on a shared branch, unless that branch was created from the deploy branch.
- Publish to … sends the changes to the deploy branch, putting them in production. It’s the default when you’re working on the deploy branch itself or on a shared branch created from it. Otherwise, it’s in the menu next to the button.
- A GitHub branch protection rule or ruleset on the deploy branch requires a pull request, reviews, or status checks, and Cube’s GitHub access can’t bypass it.
- Allow merging to this branch is turned off on the Build & deploy tab of the Settings screen.
- Leave it empty, and the agent writes the message from the changes when they’re sent.
- Click Write the message with AI to get the agent’s message in the field, so you can read and edit it first.
- If AI is not available, or the agent cannot write the message, the commit gets
Git’s default merge message, such as
Merge branch 'my-branch' into master. This applies to Commit too: Cube keeps your changes on a personal development branch and merges it into the branch you’re working on. The changes are sent either way.
Updating the branch
When there are changes in the parent branch, you can update your active branch by pulling changes from the parent branch. If your active branch got updated in the connected repository, you can update it by pulling changes from the remote.Resolving conflicts
In some cases, you may encounter conflicts when merging or pulling changes from the parent branch or remote. If this happens, you’ll see a warning about conflicts in the actions bar. You’ll then be able to either resolve them manually or discard the changes.Deep-link into development mode
You can link directly into development mode on the Semantic Model IDE by adding query parameters to the page URL:?branch=<name>switches to the given branch, entering development mode if you’re already in it (or staying read-only otherwise).?devmode=trueenters development mode on the current branch. Combine it with?branch=to enter development mode on a specific branch in one step:
Finding endpoints
In Development Mode, you’ll have dedicated endpoints that will track the branch you’re on. To see them, open the Status page and click API credentials. Read more about the available endpoints on the Environments page. An embed session can point at your branch as well: pass its name asbranchName and the embedded content queries your development environment
instead of production. That only holds while you’re in development mode on the
branch — for a branch an embedded app should reach at any time, enable its staging
environment instead.
Behavior with CLI deployments
Development mode is fully available on deployments that are configured to deploy with CLI: you can enter dev mode, switch branches, save and commit changes, and merge into the production branch from the Cube Cloud UI. However, on CLI deployments, none of these actions trigger a production build or redeploy — production only changes when somebody explicitly runscube deploy against the deployment. CLI builds use the uploaded project;
include UI changes in your local project if you want them in production. See
Deploy with CLI → Development mode for the full
behavior.