Docs / Shipping targets

Shipping targets

Shipping is the last stage of every task. Your team never pushes, tags or deploys; ThreadGrid's own ship step does, using only the targets you turn on. Set them per project in Settings → Shipping.

The ship steps

They run in this order. Each one is a switch.

StepWhat it doesDefault
Merge into baseMerges the task's branch into your base branch (usually main)On
Push to remotePushes the base branch to originOn if the repo has an origin remote
Open a GitHub pull requestOpens a PR for the change instead of, or as well as, merging locallyOff
Tag a releaseBumps the version, writes the CHANGELOG entry, tags it and publishes a GitHub releaseOff
Deploy with CoolifyStarts a Coolify deploy and waits for it to come up healthyOff
Clean up branchesDeletes the task's worktree and branch after it shipsOn

The base checkout has to be clean for a merge, so commit or stash your own edits in that folder before you approve a ship.

Pull requests and releases

These need the GitHub CLI, signed in:

brew install gh
gh auth login

Releases bump the version from the size of the change. You can fix the bump to patch, minor or major in Settings → Shipping. The release notes are written from the tasks that went into the release, and they're what the Log shows under Changelog.

No GitHub repo yet? Create a private repository in Settings → Shipping makes one with gh and adds it as origin.

Coolify

To deploy after every ship:

  1. In Settings → Shipping, turn on Deploy with Coolify.
  2. Enter your Coolify URL and the Application UUID of the app to deploy.
  3. Paste an API token. It's stored in the macOS Keychain, never in the project.
  4. Press Test connection.

After the push, ThreadGrid starts the deploy, waits up to 15 minutes for it to finish and then checks the app's health for up to 3 minutes. The result message shows the deploy's state as a chip.

21st.dev

21st.dev gives designer and frontend teammates a library of polished UI components. Add it to Claude Code once with your key:

claude mcp add --scope user --transport http 21st https://21st.dev/api/mcp --header "x-api-key: YOUR_KEY"

Settings → Integrations shows Connected once Claude Code has it. It's the one outside MCP server teammates can use without you allowing it; allow others in Settings → Integrations.

When a ship fails

  • Before the merge (a conflict, a dirty base checkout, a failing check): nothing is changed. The task goes to Needs you with the reason; fix it and press Retry.
  • After the merge (the push, the release or the deploy fails): the change is already in your base branch, so the task is marked shipped with issues and the team opens an urgent fix task straight away.

Something unclear or out of date? Email [email protected].