Sapling and stacks
Use the Sapling client and Smartlog when your work is naturally a dependency-aware stack.
Start with the repository command
Use the Sapling command from the repository’s Clone menu:
sl clone <repository-command-from-noumena-code>
cd <repository>
sl
The plain sl command opens Smartlog-style history in the terminal. It should show your current head, its ancestors, and the remote context needed to orient yourself.
Create and inspect changes
sl status
sl diff
sl commit -m "Describe the change"
sl smartlog
Sapling tracks heads without requiring you to create a named branch for every small change. Build a stack by creating related commits in order, then inspect the whole stack before submitting it for review.
Shape a stack
Common operations include:
sl amend
sl absorb
sl split
sl fold
sl rebase
Use these operations deliberately: a split or rebase changes the review shape even when the final files look similar. Re-run checks after changing the stack topology.
Review in Noumena Code
Open the repository’s Stack Reviews page after the stack has a real base and comparison range. Review commits in order, inspect changed files and checks, and use the timeline for the decision. Keep one coherent unit of work in one review rather than creating parallel reviews for each small correction.
Sapling and JJ together
JJ is the drafting interface for change-oriented work; Sapling is the promoted stack and review interface in the supported Noumena workflow. Do not copy patches between clients to simulate promotion. Use the supported client flow for the repository you are working in, then verify the resulting stack in the web app.
Further reading
For the general client, see the public Sapling getting-started guide and Sapling overview.