Shipping

When a card is Ready to ship, the Now box offers Not right and Ship it ▾. Ship it merges; the ▾ menu has the other ways.

Choice	What happens
Ship it	Merges the card into your integration branch.
Ship as a PR	Pushes the card’s branch and opens a pull request on GitHub.
Merge when checks pass	In the same menu. With a pull request, GitHub merges it by itself once its checks pass. Remembered for this workspace on this computer. Pro and Team.

The card follows its pull request: if GitHub reports failed checks or requested changes, the card tells you and can send what’s needed to the Builder.

Without GitHub

A repository with no GitHub remote shows neither pull-request option: Pull requests need a GitHub remote, and this repository has none: Ship merges the card here.

After shipping

The card moves to Done: Shipped · v2.4.1, or Merged · #29 for a pull request. Its Now box says, for example, Shipped in v2.4.1 on 2 Oct.
Its copy of the repository moves to the trash folder and is deleted after 7 days. The branch is kept.
Shipped cards are archived after 14 days.