Work on Cassis branches
In an app-managed project, use a Cassis branch when a change needs several edits, a test question, or its own eval run before it goes live.
- Create
- Use the branch switcher in the context header. The branch starts from the current context.
- Edit
- Explorer and Assistant edits stay on the branch. On a branch, the Assistant applies each change as it goes and shows its diff; on main, it proposes changes for approval instead.
- Test
- Run evals against the branch, or ask a question in a chat on the branch.
- Merge
- Choose Merge into main. Merging publishes a new version, which is when answers change, and closes the issues whose Fix in chat conversations made the changes.
A branch that falls behind main keeps taking edits. It is blocked only when main has published a change to the same part of the context; then review the branch or start a new one.
After the merge, verify the answer as in step 4 of the app workflow. On a git-managed project, use a Git branch and pull request instead: Curate a git-managed project.