04 - Commit and Ship Work#

Once you've reviewed an agent's changes and they pass your checks, commit the work and move it toward production. Helmor supports the full path from local commit to pull request.

Commit locally#

Open the workspace with reviewed changes.
Stage the files you want to include (or stage all).
Write a commit message — the session history provides good context for what changed and why.
Commit. The changes are now part of the workspace branch's Git history.

Push and open a PR#

If your repository is GitHub-connected:

Push the workspace branch to the remote.
Open a pull request from Helmor's workspace view.
The PR targets whatever branch you configured when creating the workspace (typically main).

Helmor attributes commits to your GitHub account, so the PR appears as your work on GitHub.

Pre-commit checklist#

Before committing, confirm:

The diff matches the original task — no unrelated changes slipped in.
Tests pass (bun run test, cargo test, or your project's equivalent).
Linting passes — no new warnings introduced.
The session history explains the change well enough for a teammate to review the PR.

After shipping#

Archive the workspace — frees the worktree and removes clutter from the sidebar. In worktree mode, the branch is also deleted.
Keep the workspace open — if you expect follow-up work on the same branch, leave it active.

Partial commits#

If only some of the agent's changes are ready, stage individual files or hunks. Commit the good parts and continue the session to refine the rest.