Checks and Ship

Checks gathers every signal that decides whether the workspace can merge, then boils them down to one verdict. The verdict picks the single action you can take right now, so you never get a menu of half-usable buttons.

What blocks a merge

A blocker is anything still open that should stop a merge. You clear one on purpose: nothing gets waved through quietly, and the verdict counts what's left while any are open.

• Todos are work items that block the merge, added by you or by the agent. The workspace stays blocked until they're checked off, so known unfinished work can't ship by accident.
• Check runs are the branch's automated signals: CI, lint, build, test. Each one shows its state and links to where it came from.
• Git status is where the branch stands against the base branch. Uncommitted changes, commits ahead or behind, each one you can act on separately.

Point the base branch somewhere else here if the change should merge into something other than the repository's default branch.

Ship

Ship runs for real, through git and your GitHub connection. The verdict gives you one step at a time.

Everything runs as your connected GitHub account. The pushes, the pull request, and the merge are authored as you, and branch protection still applies. A rejected push or a merge conflict shows up in Checks instead of passing quietly.

After a merge goes through, the workspace shows Merged. If you set the repository to, it archives itself.