A GitHub Action that sends Discord notifications from your CI/CD workflows using Discord webhooks.
Ilshidur/action-discord is a GitHub Action that sends notifications to Discord channels from CI/CD workflows. It solves the problem of teams needing real-time updates about GitHub workflow events by providing a simple integration with Discord's webhook API. The action automatically formats messages with GitHub event data and supports advanced features like embeds and mentions.
Development teams using GitHub Actions who want to receive workflow notifications in their Discord channels, particularly DevOps engineers and project managers coordinating deployments.
Developers choose this action for its simplicity and reliability—it's a focused solution that handles the Discord integration seamlessly while supporting all GitHub event types. Unlike generic notification tools, it's specifically optimized for the Discord webhook format with built-in GitHub payload parsing.
🚀 GitHub Action that sends a Discord message.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Setup requires only a Discord webhook URL and basic YAML configuration, making it easy to implement for standard notifications without complex dependencies.
Automatically inserts GitHub event payload into messages using template variables like {{ EVENT_PAYLOAD.repository.full_name }}, as shown in the usage examples, reducing manual data handling.
Supports Discord embeds and mentions through environment variables, allowing for advanced formatting and user alerts without modifying the action code.
Works with all GitHub workflow event types by leveraging Discord's GitHub-compatible webhooks, ensuring it can handle various workflow scenarios out of the box.
As a Docker container action, it only runs on Linux environments, excluding Windows and macOS GitHub-hosted runners, which limits flexibility for mixed-OS teams.
Arguments are passed via the 'args' key, and the TODO list notes the need to switch to the 'with' keyword, indicating a non-standard or less intuitive setup compared to other actions.
For advanced features like embeds and mentions, users must manually construct JSON strings, relying on external documentation, which can be error-prone and time-consuming.