Give every finding a clear next step.
Choose what starts a chain, the steps it takes and when it stops. Keep a Slack card current, remind a reviewer, announce a deployment or deliver a saved report.
Review the steps before enabling. Chains that act on GitHub require a successful dry run.
One trigger. Ordered steps. Time gates.
Every chain has the same shape, so every chain reads the same way in the list, in the activity log and in the dry run.
One event family per chain: a pull request opened, a review requested, a rule violated, a deployment review requested, a workflow failed, or a schedule. Scoped to a team, a repository or a path. Conditions narrow it further.
Up to eight, in order, each with a timing that never decreases. Notify to Slack, Linear, Jira or email. Wait for something to happen. Act on GitHub: a comment, a label, a failing check. Guards are checked when a step is due, not when the chain starts.
A review submitted, a pull request merged, an approval given, a thread resolved. When it happens, the chain stops and the live card shows the outcome. Nothing more is posted.
Three ways a step can speak.
Live card. One Slack message or Linear resource, kept current as the pull request changes. Email cannot use live card.
Escalate once. Posts once, then replies in that Slack thread or Linear comment, or sends a follow-up email. Does not edit the live card.
Announce. A new Slack message, Linear comment or email every time the step matches. For changelogs and reports.
Start from a chain that already works.
Templates prefill the trigger and steps. Adjust the available settings; fixed fields keep each template’s purpose clear.
One Slack message per pull request, kept current. After 12 hours without a review, the reviewer is reminded in the same channel.
Direct messages to the reviewer, then the repository owner, in Slack. Only review requests with the required confirmed Slack links can receive reminders.
Wait up to two hours for approval, then message the approver, then the repository owner.
When a high-severity rule fires: a Warestack comment on the pull request, a failing check named for the rule, an announcement.
Message the author, wait two business days for the threads to resolve, message again, then the team lead.
Wait for the deployment to associate pull requests, then announce the changelog to a channel.
Run a saved report on a schedule, optionally write a brief, and deliver rows, CSV or the brief to up to four addresses.
Chains that touch GitHub are rehearsed first.
A dry run shows the steps, destinations and actions the chain would take. Nothing is sent.
Required for any chain that comments, labels or fails a check on GitHub. Notify-only chains can be enabled from the list.
If one run would act on more than the cap you set, the chain pauses itself and messages the admins instead.
Waits and delays can count business hours only, in your timezone, so nobody is paged at 3am by a 12-hour timer.
Every run is a row: which chain fired, on what evidence, which surface it reached, what happened next.
Your first chain in five minutes.
Save a Slack address, create the live card chain, open a pull request. The card appears, and keeps itself current.
