Stash

Overview

A stash is a saved snapshot of your pending work. It lets you pause a change list and return to it later without submitting to the server.

Stashes can be stored locally or on the server. The Stash view can show both, so you can manage personal work snapshots and shared server-side snapshots from one place.

When you use it

Use a stash when you need to switch tasks quickly or when work is not ready to submit but must be preserved.

What you can do here

• Create a stash from a change list
• Save and browse stash revisions, and choose a specific revision when needed
• Restore a stash to continue work (retrieving directly from a stash item restores its latest revision by default)
• Remove stashes you no longer need
• View both local and server stashes in one UI

Stash revisions

Stashes can have revisions, so you can update an existing stash incrementally instead of replacing it entirely.

This lets you keep one stash as the anchor for a task while still tracking newer snapshots over time.

From a stash, you can save new revisions and browse previous revisions directly in the same workflow.

When you retrieve a stash item, Kimura detects cases where applying it could overwrite local changes. In those cases, it offers to save your current local changes into another local stash first, so work is not lost.

Visibility and access

Server stashes follow access rules. You only see server stashes that are accessible to your user account, based on your permissions and stash visibility scope.

Because they are shareable and access-controlled, server stashes are often used for review workflows, build validation, and similar pre-submit checks.

Compatibility with your workspace

Some stashes might get created with a different repository links (repository map) configuration than your current workspace.

When a stash is not compatible with your current workspace mapping, affected stash files are inaccessible and displayed in red in the Stash view.

Stash details shown in the UI

Each stash displays key metadata, including:

• Storage location (local or server)
• Owner (who created it)
• Creation time (when it was created)
• Repository map used when the stash was created
• Description
• Number of revisions captured in the stash

Typical flow

1. Create a stash from your active change list.
2. Switch to another task or workspace.
3. Restore the stash when you are ready to continue.