On Deck

For each destination, On Deck shows the commits that have merged into its branch but haven't shipped yet — so you can see what's about to go out.

How it works

Shipyrd compares the SHA of the latest deploy on a destination against the head of the branch that destination tracks. The “On Deck” link on the dashboard points at GitHub’s compare view between those two refs, so you get the full list of merged commits and PRs waiting to ship.

<repository_url>/compare/<latest_deployed_sha>...<branch>

There’s no separate background job — the link is generated on demand whenever the dashboard renders, so it’s always current.

Configure it

On Deck needs three things to work for a destination:

  1. The application’s repository URL. Set this on the application’s settings page in Shipyrd. It should be the public GitHub URL, e.g. https://github.com/myorg/myapp. Without it, On Deck has nowhere to compare against.

  2. A branch on the destination. Each destination tracks one branch — typically main for production and a different branch (or the same) for staging. Set it on the destination’s settings.

  3. A real deploy. On Deck only shows up after at least one deploy has been recorded with a git SHA. The version field on the deploy is what Shipyrd uses as the “from” side of the compare.

Verify it worked

Open the application in Shipyrd and look at the destination card. Once a deploy is recorded, an On Deck link appears that opens GitHub’s compare view in a new tab. If the link doesn’t appear, one of the three pieces above is missing.