[PR #693] Add notify-cascade to Notifications and Messages #10875

New Issue

GiteaMirror · 2026-06-09T20:10:42-05:00

GiteaMirror commented

2026-06-09 20:10:42 -05:00

📋 Pull Request Information

Original PR: https://github.com/sdras/awesome-actions/pull/693
Author: @kai-learner
Created: 2/22/2026
Status: 🔄 Open

Base: main ← Head: add-notify-cascade

📝 Commits (1)

fb62b17 Add notify-cascade to Notifications and Messages

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 README.md (+1 -0)

📄 Description

What is notify-cascade?

notify-cascade is a GitHub Action that sends notifications to Slack, email (SMTP), and custom HTTP webhooks — all in one step, fired in parallel.

Why it's a good addition

Most teams need to notify 2-3 channels on CI events. Today they chain separate actions for each one. notify-cascade handles all three in a single step with a simple YAML config:

- uses: kai-learner/notify-cascade@v1
  with:
    message: 'Deploy to production succeeded 🚀'
    slack-webhook: ${{ secrets.SLACK_WEBHOOK }}
    email-to: team@example.com
    smtp-host: smtp.gmail.com
    smtp-user: ${{ secrets.SMTP_USER }}
    smtp-password: ${{ secrets.SMTP_PASSWORD }}
    webhook-url: ${{ secrets.OPS_WEBHOOK }}

✅ All channels fire in parallel (non-blocking)
✅ Per-channel status outputs (sent / skipped / failed)
✅ Rich Slack block-kit messages with repo/run context
✅ HTML + plain-text email, customisable subject
✅ Custom webhook headers and body templates with {{message}}, {{repository}}, etc.
✅ 10 unit tests, CI on Node 20 + 22, MIT license, node20 runtime

It fits under Notifications and Messages alongside the existing Slack and email actions.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/sdras/awesome-actions/pull/693 **Author:** [@kai-learner](https://github.com/kai-learner) **Created:** 2/22/2026 **Status:** 🔄 Open **Base:** `main` ← **Head:** `add-notify-cascade` --- ### 📝 Commits (1) - [`fb62b17`](https://github.com/sdras/awesome-actions/commit/fb62b179de6d5b8442ebf4572a240f446cf8e421) Add notify-cascade to Notifications and Messages ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `README.md` (+1 -0) </details> ### 📄 Description ## What is notify-cascade? [notify-cascade](https://github.com/kai-learner/notify-cascade) is a GitHub Action that sends notifications to **Slack**, **email (SMTP)**, and **custom HTTP webhooks** — all in one step, fired in parallel. ### Why it's a good addition Most teams need to notify 2-3 channels on CI events. Today they chain separate actions for each one. notify-cascade handles all three in a single step with a simple YAML config: ```yaml - uses: kai-learner/notify-cascade@v1 with: message: 'Deploy to production succeeded 🚀' slack-webhook: ${{ secrets.SLACK_WEBHOOK }} email-to: team@example.com smtp-host: smtp.gmail.com smtp-user: ${{ secrets.SMTP_USER }} smtp-password: ${{ secrets.SMTP_PASSWORD }} webhook-url: ${{ secrets.OPS_WEBHOOK }} ``` - ✅ All channels fire in parallel (non-blocking) - ✅ Per-channel status outputs (sent / skipped / failed) - ✅ Rich Slack block-kit messages with repo/run context - ✅ HTML + plain-text email, customisable subject - ✅ Custom webhook headers and body templates with `{{message}}`, `{{repository}}`, etc. - ✅ 10 unit tests, CI on Node 20 + 22, MIT license, node20 runtime It fits under **Notifications and Messages** alongside the existing Slack and email actions. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-06-09 20:10:42 -05:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/awesome-actions#10875