Skip to content

Work with Git and pull requests

Nerve discovers repositories in the project and shows branch, working-tree changes, and recent commits. Available UI operations include branch creation and switching, stage/unstage, stash, discard, fetch, pull, push, and sync. The Staged and Unstaged headings expose visible whole-group actions; right-click a group, folder, or file for scoped actions. Destructive discard asks for confirmation. Folder expansion is remembered locally per repository and change area.

Stash actions preserve the area where you invoke them: stashing from Staged saves staged changes, while stashing from Unstaged saves unstaged and untracked changes without changing the index. File and directory actions limit the stash to that path. When a repository has saved stashes, Stashes (N) opens a manager where you can apply a stash without removing it or permanently drop it after confirmation.

These Workbench operations are server routes, not agent tools. An agent uses Git indirectly through finite Bash commands, subject to its mode and permission policy.

Nerve workbenchNerve Git panel showing repository status, staged and unstaged changes, and commit historyNerve Git panel showing repository status, staged and unstaged changes, and commit history
What to notice: Repository state and scoped actions stay visible beside the conversation, but destructive discard still requires confirmation.

GitHub support requires:

  1. a Git repository with a GitHub remote;
  2. the gh CLI installed;
  3. gh auth login completed for the relevant host.

The Pull Requests panel shows status and lists. A PR tab can display the conversation, commits, checks, and changed files; it can check out or merge when the repository state permits.

Checkout and merge can modify local or remote state. Read the confirmation, working-tree status, target/base branch, and check results before proceeding.

Nerve workbenchNerve pull request tab showing a GitHub pull request conversation, checks, commits, and changed filesNerve pull request tab showing a GitHub pull request conversation, checks, commits, and changed files
What to notice: The pull request tab brings review context, checks, commits, and changed files together before checkout or merge actions.

Contextual built-in suggestions can appear when Git state calls for committing changes, moving work off a base branch, or creating a PR. They insert agent instructions; they do not bypass Git review or tool approvals.