Notifications
The Unity CI/CD Templates support optional notifications to Slack and Discord using webhooks.
When configured, the pipeline sends detailed messages after each run to keep your team informed.
Here’s an example of a Slack notification showing:
- ✅ Release succeeded
- ❌ Deploy failed on a specific target
- Commit info, release link, and pipeline link
- A per-target deployment summary table
The notification includes:
- Tests status → failure notification on release and RC builds
- Release status → success, failure, or partial (release ok but deploy failed)
-
Deploy target summary → table showing each target (e.g.,
gh-pages,itch.io) with ✅ or ❌ - Commit + branch details → commit hash, branch, and version
- Quick links → to the GitHub Release page and the pipeline run
| Platform | Status | Setup Requirement |
|---|---|---|
| Slack | ✅ Supported | Add SLACK_WEBHOOK secret |
| Discord | ✅ Supported | Add DISCORD_WEBHOOK secret |
| Microsoft Teams | ⚠ Planned | Not yet implemented (see roadmap) |
-
Create a webhook
- For Slack → use an Incoming Webhook URL
- For Discord → create a webhook in your Discord server
-
Add the secret to your GitHub repo
-
SLACK_WEBHOOK→ for Slack -
DISCORD_WEBHOOK→ for Discord
-
-
That’s it!
If the secrets exist, the pipeline will automatically send notifications after release and deployment.
Want to customize the message formatting?
- Slack messages → use colored attachments (
good,danger, or neutral) - Discord messages → simple markdown text
Advanced users can modify:
.github/actions/generate-notification- Workflow files in
.github/workflows/step-5-notify.yml
We welcome PRs to improve or extend platform support!
- Microsoft Teams integration
- Email notifications (optional)
Check the Roadmap or open a Discussion if you want to contribute!