OrcaORCA
Star us4.9k

Commit & push from Orca

You can commit, push, and open the review without leaving Orca. The commit panel lives next to the diff viewer and is designed for the common case — review, stage, commit, push, move on.

Commit

  1. Stage changes by hunk or by file from the diff.
  2. Write a commit message in the bottom panel, or use Generate with AI when you want Orca to draft one from the staged changes.
  3. Hit Commit (Cmd-Enter).

Pre-commit hooks from the repo run as usual. If a hook fails Orca surfaces the output inline.

When a commit fails, use Fix with AI from the failure details to start the default agent in the active worktree with the hook output, attempted commit message, and staged file list. The agent gets a repair prompt only — it is not asked to bypass hooks, commit, push, or open a review.

Push

Push pushes the worktree's branch to origin, setting upstream the first time. If the branch is behind, Orca will not silently force-push.

When you've rewritten history (rebase, amend, squash) and the remote only has older copies of your local commits, the Source Control panel surfaces Force push with lease as an explicit, separate action — never as a fallback for plain Push. The label shows the commit count being replaced and the upstream branch name so you know exactly what's about to change. Force push uses --force-with-lease, so a stale local view of the remote aborts the push instead of clobbering someone else's commits.

Open a hosted review

After the branch is pushed, use the Source Control panel's hosted review action to create the pull request or merge request. Confirm the base branch, title, description, and draft state before submitting.

Use Generate pull request details with AI in the create-review dialog when you want Orca to draft the base, title, description, and draft state from the branch diff and commits. Review the fields before creating the review.

Amend

Amending is explicit — Commit → Amend. Orca won't amend commits that have already been pushed unless you confirm.

Source control panel

The sidebar Source Control panel exposes the same actions without leaving your current view: stage and discard files, write a commit message, and run Commit, Push, Pull, or Sync as one-click actions. Paths render as UTF-8 even when they contain non-ASCII characters.

The panel's primary button at the bottom shifts with state so the next useful action is always one click away: Stage Files when there are unstaged changes, then Commit, then Push / Pull / Sync depending on how the branch sits against its upstream.

When a merge, rebase, cherry-pick, or revert leaves conflicts, Source Control shows Resolve with AI next to Review conflicts so you can either hand the conflict set to an agent or inspect it yourself before continuing. For an in-progress merge or rebase you no longer want, use Abort merge or Abort rebase from Source Control.

Next steps