Cleanup and backups

Cleanup is the third tab of the repository, for freeing space in the open project. It scans in the background and fills in as it reads.

Ready to clean lists what can go, each row with its size and action:

• Finished worktrees — worktrees whose work is already in the default branch.
• Merged branches — merged and not checked out.
• Build output and packages — ignored folders the next build or install writes again, such as build, node_modules and Pods. Tracked files and .env stay.
• Chats — old chats go to the Trash, or only what their next run writes again.
• Backups, stale worktree entries and repository objects (a partial clone keeps old file versions on the remote until needed).

Check first lists worktrees and branches that hold work the default branch lacks; each opens the usual confirmation.

Suggestions read the repository itself: build output tracked in Git, likely secrets tracked by name, system and editor files such as .DS_Store, and build folders .gitignore misses. An action stages its change for you to commit in Changes.

With Automatic backups on, ffgit saves a recovery copy before switching branches, discarding, stash, merge, rebase, pull and other commands that rewrite files. Copies are stored in the project’s .ffgit/backups folder until you delete them.

From Backups you can:

• Verify a copy;
• Restore to new folder… — saved files and staged changes, never over your work;
• Export… a copy to move it to another computer, or Import backup…;
• Create backup on demand and clean up old copies.