Branches let you develop separate versions of a cloud project. Stashes keep unpublished work for an explicit later restore.
Check the branch you are editing
The open working copy determines the editor's branch. Browsing another project or branch in Workspaces is not the same as opening it.
History follows the selected branch's ancestry. A new branch may inherit commits originally authored elsewhere. A design variant describes fitted components; it is not a version-control branch.
Create or switch branches
- Open the intended project and inspect its current branch and saved changes.
- Create a named branch with the offered base revision, or choose an existing branch from the picker.
- Read the native review, including the source, target and unpublished work.
- Confirm the intended action.
- Check that the target branch actually opened before editing or sending a new design request.
If branch details are unavailable, do not assume the current branch or displayed failure is harmless. Check the matching outcome rather than repeat the switch.
Choose where unpublished changes go
In builds offering the advanced choice:
- Move changes carries the reviewed unpublished source delta to the target branch through a three-way merge.
- Leave changes here keeps that work in a stash associated with the source branch and requests the target without carrying it.
- Stay declines the transition.
Move and Leave do not Push, discard work or change ignore rules. Save intended editor changes before review. The current native Move changes path refuses unpushed local commits. Push them on the source branch first, then review the switch again, or choose Leave changes here to preserve them in a stash. A refusal is not permission to bypass preservation.
If Commit or Push is offered inside the switch choice, read the displayed continuation wording. Standalone Commit/Push act on the source branch; pending switch behavior is build-dependent. Confirm the resulting open branch, not just the command's completion.
Move compares the source's published base, parked source work and target saved content. Overlaps use conflict review; do not automatically select incoming content. Parking alone does not prove that switching or application finished.
Restore a stash
- Return to the branch associated with the stash.
- Open Stashes and select the intended saved entry.
- Choose Restore stash and inspect the current destination work.
- Review any overlaps and apply the intended result through the conflict flow.
- Inspect the restored files and editor before committing or publishing.
Restore is explicit, not automatic on return. Multiple entries can coexist. The advanced restore flow performs a three-way merge of the parked base/work with current destination content, including published changes, unpushed local commits and saved destination edits. It preserves the destination's current local commit and applies restored content as uncommitted edits, not a cloud revision.
If your build requires an update or refuses a destination state, follow that reason; do not force a clean-looking state by discarding work. Unknown or unverified application retains the stash for recovery.
Discard only the work you intend
Discard changes removes uncommitted changes and eligible untracked, non-ignored files; it keeps unpushed commits. Discard stash deletes the selected separate parked copy.
Both are destructive choices. Read the confirmation and preserve a backup if you might need the work. Do not discard a stash merely because a switch appears to have succeeded.
The advanced store supports up to 64 retained stashes per project. At the limit, a new park is refused before switching; inspect entries and explicitly discard only work you no longer need.
Branch deletion is also permission- and state-dependent. The default/current branch, active checkouts or open PR references can prevent deletion. Do not delete a branch as a substitute for resolving unpublished work.
If switching or restoring does not finish
Park preserved means local work was retained; it is not target-open success. A partially applied Move or Restore needs the matching conflict/recovery flow. Keep the stash and original operation, then use Workspaces recovery.
Do not automatically restore, discard or repeat the switch while its outcome is unknown.