General settings

Innesta ▸ Settings… (⌘,) opens Innesta’s preferences, in five tabs: License, General, AI, Accounts and Privacy. They apply to every repository.

Anything that belongs to one repository is in that repository’s own settings, reached from the gear beside its name in the sidebar, and there are three of those: Remotes, GitFlow and AI.

What General holds

• Show Menu Bar Extra — whether Innesta puts a status item in the menu bar.
• Show projects in Spotlight — whether the branches and newest commits of your projects can be found from Spotlight. On to begin with; switching it off deletes everything Innesta had handed to Spotlight. See where your data goes.
• Auto-stash on branch switch — whether switching branches with uncommitted work stashes it for you rather than stopping. Whether that stash comes back when you return to the branch is decided in the confirmation itself, which remembers the answer.
• Merge strategy.
• Keep recovery backups, in the Recovery card — how long the safety net keeps what it saves.
• Clone Location — the parent folder new clones are suggested into. Use Default puts it back.
• Installing the command line tool.

The default merge strategy

Which of merge, squash merge or rebase the branch menu’s Use Default action performs. Saved globally, so a house style is set once.

How long backups are kept

Keep recovery backups is one choice for every repository — one, three, seven, fourteen or thirty days — and seven is where it starts. There is no “for ever”. It covers everything the safety net makes — the backups of deleted branches, discarded changes and hard resets, and the copies a discard puts in the Trash — and what has expired is cleared when a repository is opened or refreshed. A backup that could not be cleared is reported and left where it was, not deleted half-way.

Your Git identity is not here

The name and email address that go on your commits are Git’s own global configuration, and Innesta asks for them once, in Git Identity during onboarding, because a repository with no identity configured fails at the first commit with an error that does not obviously say so. Changing them afterwards is git config --global, or whatever you already use for it.

To use a different identity in one repository, see use a different identity for one repository.

Nor is the diff layout

How much context a diff shows is chosen in the diff’s own toolbar rather than here — the choice is in front of you while you are looking at the thing it changes. It is remembered across repositories once you make one; until you do, the picker reads Repository Default and each repository’s own Git configuration decides.

Whether long lines wrap is another of those: the toggle sits beside the context picker, and the choice is global.

Whether a diff reads inline or side by side is not a preference at all. The column is inline and the Diff Review window is side by side.

Nor is commit signing

The signing toggle sits beside the commit message, and its initial state follows your commit.gpgSign setting rather than a preference of Innesta’s, so a repository configured to sign signs.

Diagnostics

In Privacy, as Usage Diagnostics, and off by default. See where your data goes for what is recorded when it is on — and what is never recorded either way.