Repository navigation
Stashes and Tags
Garrett Speager edited this page Oct 6, 2026
·
2 revisions
Both panels live in the Nav Pane.
A stash shelves your current uncommitted changes so you can come back to a clean working tree, then bring them back later.
- The Stash button is disabled when your working tree is already clean — there'd be nothing to stash.
- Add an optional message, and choose whether to include untracked files.
- Keep staged changes stashes only what isn't staged, leaving your staged changes in place.
- To stash just some files, select them in Working Copy — across Staged and Unstaged if you like — and choose Stash from the right-click menu. Only those files go into the stash; anything else you've staged stays staged.
- Show changes on a stash lists the files it changed, with a diff for each — including untracked files it saved.
- Each stash entry can be Applied (kept in the stash list), Popped (applied and removed), or Dropped (removed without applying — this is destructive and asks for confirmation).
Tags mark a specific commit, typically for a release.
- Create a tag against any commit, with an optional message — leaving the message blank creates a lightweight tag instead of an annotated one.
- Annotated tags can be expanded to show their full message.
-
Push sends a tag to your remote (defaulting to
originor your first configured remote). - Delete removes a tag locally — it doesn't affect any copies already pushed to a remote. This can't be undone from within the app, so it asks for confirmation first.
- Delete on remote removes a tag from the remote it was pushed to, so it doesn't come back the next time you fetch.
Getting started
Everyday work
- Working Copy & Staging
- The Diff Viewer
- Committing Changes
- Branches
- Remotes & Syncing
- Signing In to Remotes
- Worktrees & Submodules
- Search in Files
History
When things go wrong
Insights
Configuration