What does Innesta not do?
The things it deliberately leaves to Git, to the provider, or to you.
Worth knowing before you go looking.
Not in the app
- Interactive rebase. Reordering, editing or squashing commits within a branch is a command line operation. Innesta shows a rebase in progress and resolves its conflicts.
- Cherry-pick, as a command. A cherry-pick started elsewhere is shown and resolvable here.
- Submodules.
- Worktrees, as a command — though a worktree’s directory opens like any other repository.
- A
support/GitFlow workflow. The prefix is stored for compatibility; there is no lifecycle for it. - Starting a branch anywhere but where you are. New Branch… branches
from the commit you have checked out. Naming an older commit — to recover one
from the reflog, say —
is
git branch <name> <hash>.
Read-only on the provider
Pull and merge requests and pipelines can be read and opened on the provider. They cannot be approved, commented on, merged, or re-run from Innesta. Review is a conversation, and half a conversation is worse than a link to all of it.
Only GitHub and GitLab, for the API
Provider links work for GitHub, GitLab, Bitbucket and Azure DevOps. Reading requests and pipelines works for GitHub and GitLab. GitHub Enterprise Server works through the API with a token you supply, and not through OAuth.
Not on your Mac
- Intel Macs. Apple Silicon only.
- macOS 13 and earlier. macOS 14 Sonoma is the floor.
- Anything without
git. Innesta drives the system binary rather than reimplementing it.