Does Innesta change my repository?

Opening a repository changes nothing about it. Innesta reads it, and does not write until you run an operation.

What it does add, over time, is one thing: a full-text search index at .git/innesta. That is a cache — deleting it costs nothing but the time to rebuild it, and it contains nothing that is not already in the repository. It is inside .git, so it is never committed and never pushed.

No configuration is rewritten behind your back. Innesta reads Git’s configuration to decide how to behave — the signing default, the push destination, GitFlow’s branch names — and writes only the keys you change, in the scope they belong to.

The operations that destroy something

Three, and each takes a backup first, kept in Recovery for seven days unless you set it otherwise:

• discarding changes,
• a hard reset,
• deleting a branch.

Rewriting history is a separate category, and everything in it asks first. Amending and force pushing show you a diff of what they would do before you agree; a rebase and a merge confirm without one, because what they will produce is not knowable until they have run.

Force push is the only operation whose effect is on a machine that is not yours, which is why it is the one with the most friction in front of it — and why it is always --force-with-lease.

And your other tools

Because Innesta drives the system git, a repository it has operated on is an ordinary repository. Nothing needs Innesta to be readable afterwards; anything you do in a terminal shows up in the app within a moment of your going back to its window, since it watches the repository while you are using it and refreshes once on your return when you are not.