Review before you merge

Inspect the complete workspace change: commits since its base, staged changes, unstaged edits and untracked files. Each category answers a different question about what will be included in the final result.

Use stage and reject controls on the current working changes. The broader review shows context; it should not be confused with the current index.

Check the result

Run the project’s tests, lint or build commands. Read their output and investigate failures. Check that generated files and credentials have not accidentally entered the change.

Select a coordinator winner

In Compare, choose Review and pick. The review identifies the winner commit and the current target branch and commit. Both checkouts must be clean, and the project must already be on the target branch; Copperbar does not switch it for you.

Select the recorded checks required for this merge. A result must still match the current source, configured command and latest run of that check. If you proceed without selected passing checks, enter a reason. This is recorded as an unchecked operator decision, never as a passing test.

Approve and merge authorizes this exact review once. Changes to code, target, check evidence or configuration require a fresh review. Copperbar stops this run's child sessions before landing and refuses to interrupt unrelated active project work. Other child branches are kept when their workspaces are safely archived. Files that use custom Git conversion filters or merge drivers require manual inspection and merging. Repositories with submodules also require manual inspection. Merely having an unused converter such as Git LFS installed does not block an ordinary repository.

The approval records local operator authority. It does not prove independent review or identify a verified human; tools with the same local access can use that authority. Check evidence covers Git-visible source, not ignored inputs, environment or external services. Separate tools outside Copperbar can still modify a repository.

Use Saved runs to return to a previous coordinator run after restarting. An unresolved landing blocks further automatic landings in the same project.

Check interrupted merge verifies whether the recorded merge exists in the intended branch history. It does not repeat the merge or archive more work. Abandon unchanged landing is available when the target is unchanged; give a reason, then review again.

If you resolved the Git state yourself, Acknowledge manual resolution records your explanation and the observed target state. It does not claim that a merge succeeded and does not change Git files. Previous pending approvals are invalidated; any subsequent landing requires a fresh review. Copperbar does not automatically repeat an uncertain merge or archive operation.

Create a pull request

Commit the intended changes, push the branch and create a pull request. GitHub integration requires the GitHub CLI to be installed and authenticated with access to the repository.

Archive the workspace only after preserving any work you need. Copperbar refuses to remove a dirty owned workspace.