Skip to content

Git Tab & Recovery

The Git/Deploy area of a project window covers day-to-day Git status plus a set of recovery surfaces for the states that come up when a pull, a push, or an integration doesn’t land cleanly.

Project window → Git tab. Lists open pull requests for the project’s remote and provides a guarded merge action — merge is a deliberate, explicit click rather than something that happens as a side effect of another action.

MCP tools: orbit_github_prs, orbit_github_pr.

When a Git pull is blocked because the working tree has uncommitted changes, the Git tab offers safe recovery actions instead of leaving you to resolve it manually from a terminal.

If a run leaves work behind without a normal commit — for example an interrupted or crashed session — Orbit surfaces recovery-ref links on the affected Pipeline card so that work isn’t stranded and unreachable.

The Git tab warns when local commits exist that are absent from the reachable remote history, and provides recovery guidance so work doesn’t sit invisible to anyone but the local machine.

MCP tool: orbit_stash_resolve also covers related stash-conflict recovery from MCP clients.

Lists the project’s available Git stashes directly in the Git tab, for inspection and recovery without dropping to a shell.

Provides operator recovery actions for every parkable publication and reachability state — the recovery path when a commit’s push or integration status is ambiguous rather than a clean success or failure.