Skip to content
OpenChamber
↑↓Navigate ↵Open escClose

Git Workflows

OpenChamber has a built-in git view so you can review changes, commit, and manage branches without switching to a terminal. Open it from the Git tab in the right sidebar.

Review and commit

The git view splits your changes into staged and unstaged:

  • click a file’s + to stage it, or − to unstage it
  • stage or unstage everything in a group at once
  • click a file to see its diff

Then write a commit message and commit. You can have OpenChamber generate a commit message from your staged changes — it uses the current session’s model, so you need a session open.

Branches and history

The git view also covers the everyday rest of git:

  • create, switch, rename, and delete branches
  • push, pull, and fetch
  • browse history and per-commit diffs
  • stash and restore changes

Pull requests

With an account connected on the project’s host, the PR tab lets you open a pull request, update it, mark it ready, or merge it. OpenChamber can write its title and description the same way as commit messages. This works on GitHub, Gitea, Forgejo, and GitLab, where the tab opens merge requests. Gerrit has its own form, Push for review. Connecting a host is covered in Git hosts.

Push for review on Gerrit

On a Gerrit project the pull request form becomes Push for review. It pushes your commits to refs/for/<branch>, which creates a change, or a new patchset of a change you already pushed. The commit message is the change’s description, so the form shows the latest commit’s subject instead of a title and body. Pick the target branch and, if you want, a topic, hashtags, Work in progress and Private. It works on the target branch itself too, the usual way to work with Gerrit.

Gerrit matches commits to changes by the Change-Id line its commit-msg hook adds to each message. If only the latest commit is missing one, Add Change-Id amends that commit after asking; nothing is pushed until you push. If older commits are missing one, the push waits until you install the hook and give each of them a Change-Id.

After the first push, the panel offers Upload patchset whenever your local commits aren’t on it yet. A change in a chain of changes shows its place in the chain, such as 2 of 3, next to its badge.

Bringing in conflicts

If a merge, rebase, or integrate hits a conflict, OpenChamber shows what’s stuck and lets you resolve it — including handing it to the agent.