| title | split |
|---|
Create a new view by forking from an existing one.
atomic split [OPTIONS] <NAME>The split command creates a new view by forking from an existing view. This is a convenience wrapper around atomic view create <NAME> --from <SOURCE>, providing a streamlined interface for the common operation of branching off a new line of work.
When you split, Atomic:
- Creates a new view with the given name
- Copies the change log from the source view (or current view if
--viewis not specified) - Optionally switches to the new view
The new view is a Draft view parented on the source, sharing the same underlying graph. No data is duplicated — only change references are copied to VIEW_CHANGES.
Name of the new view to create.
View names should be descriptive and follow a naming convention like feature-*, bugfix-*, release-*, etc.
Split from a specific source view instead of the current view.
atomic split new-feature --view mainSwitch to the new view after creating it. By default, the current view remains unchanged after splitting.
atomic split feature-auth --switch# Create a new view forked from whatever view you're on
atomic split experimental
# Created view: experimental (split from dev with 5 changes)# Create a hotfix view from the release view
atomic split hotfix --view release-1.0
# Created view: hotfix (split from release-1.0 with 42 changes)# Create and immediately switch to the new view
atomic split feature-auth --switch
# Created view: feature-auth (split from dev with 10 changes)
# Switched to view: feature-authatomic split is equivalent to:
atomic view create <NAME> --from <SOURCE>Use atomic view create directly when you need additional options like --draft, --parent, or more fine-grained control over view creation.
atomic view- Full view management (create, switch, list, delete)atomic insert- Insert changes between viewsatomic record- Record changes in the current view
atomic split --help