One message per pull request, kept current. Review reminders for the right people.
Keep one Slack card current as a pull request changes. Add review reminders for linked members, or deliver a saved report on a schedule with the rows, CSV and brief you choose.
Private channels appear once the Warestack app is invited. Direct messages reach people who have confirmed their Slack link.
Three things in the workspace.
Each is a chain step. Which channel, which people and which timing is decided on the chain.
One message per pull request, edited in place as reviews and checks change. Keep the current state visible without a new channel message for every event.
A review that has waited 12 hours, a deployment review waiting for an approver, an attention list: sent to the person who can act, visible only to them.
Scheduled reports post with the rows, the CSV and a written brief. Skip-if-empty keeps quiet days quiet.
A message reaches a person.
Warestack links GitHub identities to Slack members, so the reviewer named on a pull request is the person who gets the direct message. Members confirm their own link; admins see who is linked and who is not.
Fail closed. Review SLA chains do not guess. A reviewer without a confirmed link is reported as not reachable, and the chain says so.
Readiness, shown. Before enabling a chain that sends direct messages, the readiness card lists who would and would not receive them.
Confirm links for the people who need direct messages. Channel delivery does not require every member to be linked.
Chains that deliver to Slack.
Choose a template, review its timing and recipients, then preview the configured delivery. Direct-message steps require a confirmed Slack link for their recipients.
Direct messages to the reviewer, then the repository owner, when a review has waited. A missing recipient link is shown in readiness so you can resolve it.
One Slack message per pull request, kept current, with a reminder after 12 hours without a review.
Message the approver after two hours, the owner after four. Resolves when the review is approved.
Connected in three steps.
A space admin connects once. Addresses are shared by every chain; scope belongs to the chain.
Scopes: post and update messages in channels the app is in, send direct messages, read channel names and members. The app reads no message content.