Deploy Safety
Deploy Safety keeps your team informed and protected around production deployments. Every push to your main branch triggers instant notifications so the right people know a deploy is happening. Combined with upcoming safety checks, Deploy Safety helps prevent risky changes from reaching production without oversight.
How It Works
Deploy Safety listens for deployment-related events via webhook triggers. When a qualifying event occurs (such as a push to your main branch), TinyOps evaluates the rule conditions and fires the configured action. Template variables let you include contextual information like the commit author in your notifications.
Live Rules
Deploy Notification
Sends a Slack notification every time a push lands on your main branch.
name: deploy-notification
trigger:
type: webhook
event: push
branch: main
action:
type: notify
channel: slack
message: "Deploy triggered by {{head_commit.author.name}} on main"| Setting | Value |
|---|---|
| Trigger | Webhook (push to main) |
| Channel | Slack |
| Template variable | head_commit.author.name |
The head_commit.author.name variable is extracted from the GitHub push event payload. You can reference any field from the webhook payload using the {{field.path}} template syntax.
Coming Soon
| Rule | Description |
|---|---|
| Friday Deploy Warning | Warns (or blocks) deploys attempted on Fridays after a configurable cutoff time |
| Post-Deploy Health Check | Runs a health check 5 minutes after deploy and alerts if errors spike |
Template Variables
Deploy Safety supports template variables from the GitHub push webhook payload:
| Variable | Description |
|---|---|
head_commit.author.name | Name of the commit author |
head_commit.message | Commit message text |
head_commit.timestamp | When the commit was created |
pusher.name | GitHub user who pushed |
ref | Full ref path (e.g., refs/heads/main) |