Stashes
A stash sets your uncommitted changes aside and leaves the working tree clean. Mergepond stashes everything in one click, including untracked files, and lists the stashes in the sidebar where you apply, pop or drop them.
Where to find it
- Toolbar › Stash ("Stash all changes").
- Repository › Stash All Changes, or Command palette › Changes › Stash all changes.
- Sidebar › Stashes, shown when the repository has any.
Stashing
Stash runs git stash push --include-untracked, so new files that aren't in Git yet are stashed too rather than left behind. The button reads "Stashing…" while it works, then a toast confirms: "Stashed N changed files. The working tree is clean." Mergepond doesn't ask for a message; the stash gets Git's default one, built from the branch and last commit.
The Stashes section
Each stash is a row with its message (Git's "WIP on branch:" prefix trimmed) and how long ago it was made. Hover a row for its full message and three buttons:
| Button | What it does |
|---|---|
| Apply | Puts the changes back and keeps the stash. Toast: "Applied the stash. It is still saved." |
| Pop | Puts the changes back and removes the stash. Toast: "Popped the stash into your working tree." |
| Drop | Removes the stash without applying it. Toast: "Dropped stash “…”." with Undo. |
Undo
Dropping a stash offers Undo in its toast, which puts the stash back. See Committing for how undo works.
Worktrees instead
If you reach for stash to switch branches, a worktree may serve better: it checks out the other branch in its own folder and your changes stay put. See Worktrees and worktree setup.
Free and Pro
Stashes work the same on Free and Pro.