For the complete documentation index, see llms.txt. This page is also available as Markdown.

Stashing Changes

Overview

Stashing lets you temporarily set aside changes you've made without committing them. When you stash, your changes are removed from your files and saved for later, leaving you with a clean working state. Stashed changes are stored in temporary system folders and any stashed changes will not appear in your working directory.

If you make a commit to a branch with stashed changes they will appear as a separate branch with no name. To clear these stashed changes, you can discard or merge them later.

How to stash changes in the Desktop App

When you have changes you want to stash, you right-click on the changed file in current repository heading to reveal the context menu to make the stash

When you stash the changes, your Changes tab will appear empty.

You will also be offered an option to stash changes when switching a branch while you have uncommitted changes. If you stash changes, your new branch will show no new changes.

How to view and restore your stashed changes

Restoring a stashed change brings those changes back to your changes tab, ready for a commit. This can potentially cause a conflict if stashed changes and current changes are overlapping.

To view stashed changes in the Desktop App, select the "Stashed Changes" heading above the commit message area in the bottom right corner of the app.

Once your stashed changes are visible, you can choose to restore or discard your changes.

To discard the changes, when viewing, instead of selecting "Restore" you can "Discard". Discarding changes removes the changes entirely, meaning they will no longer be stored locally or in any temporary storage.

Last updated

Was this helpful?