Change Lists

Overview

A change list groups related edits so they can be reviewed and submitted together. It is the primary unit of work you submit to the server.

In this view, files use the same visual signals as Workspace view, so you can spot status changes and potential conflicts on files you are actively working on.

Files in your workspace change lists are visible to other users, which helps coordinate shared work before submit time.

This is also where you can add lock operations to signal your intent to modify a file and prevent other users from submitting conflicting modifications.

When you use it

You create a change list for any set of edits that should travel together, such as a feature, bug fix, or content update.

What you can do here

• Create and name change lists
• Add or remove files from a change list
• Save and browse change list revisions
• Review file signals to detect potential conflicts early
• Add lock operations on files when coordination requires exclusive submit rights
• Submit a change list when it is ready

Change list revisions

Change lists can have revisions, which lets you update an existing change list over time without replacing it.

This makes it easier to iterate on in-progress work, keep review context intact, and track how a change list evolves before submit.

Under the hood, change list revisions make use of local stashes.

Because of that, you browse change list revisions the same way you browse stash revisions.

Typical flow

1. Create a change list for your task.
2. Add files as you edit them.
3. Review the list, then submit.