Skip to main content
To follow a deploy in a conversation, insert a deployment block when it starts and push each step’s status as your pipeline moves. Members can open the release and logs, or cancel and retry, from the block.
src/app.ts
The example pushes state from a message action. In a real app, the push usually comes from a route your CI calls, using reintersect.forInstall(installId).

Props, state and actions

Props are { service, environment, version?, url?, logsUrl?, commitUrl? }. State is { status, steps, error? }:
  • status: queued, running, success, failure or cancelled.
  • steps: { label, state, description? }[], where state is any status state.
The first button in the block is the primary one, so the recipe orders the buttons by status: Retry leads after a failure or a cancel, the release link once the deployment is live, and Logs while it runs. Cancel is destructive, so it asks before it runs and can’t be primary.

Labels

title, status, open, logs, commit, cancel, confirmTitle, confirmBody, retry.