Skip to content

Add GitHub Actions workflow for Discord notifications - #11

Open
chikle9090 wants to merge 2 commits into
ruxailab:mainfrom
chikle9090:feature/discord-notification
Open

Add GitHub Actions workflow for Discord notifications#11
chikle9090 wants to merge 2 commits into
ruxailab:mainfrom
chikle9090:feature/discord-notification

Conversation

@chikle9090

@chikle9090 chikle9090 commented Dec 13, 2025

Copy link
Copy Markdown
Collaborator

Summary

This PR adds a GitHub Actions workflow that sends GitHub activity updates
(pushes, pull requests, and issues) to a Discord channel using a webhook.

Motivation

Keeping contributors informed of repository activity directly in Discord
helps improve collaboration and reduces the need to constantly check GitHub.

What’s Included

  • GitHub Actions workflow for Discord notifications
  • Supports push, pull request, and issue events
  • Uses Discord webhooks with JSON payloads

Related Issue

Closes #5 — GitHub to Discord Notification System (MS1: Discord Integration)

@Santosh69

Copy link
Copy Markdown
Collaborator

Hi @chikle9090 ,
Thanks for the PR! could you change the line breaks from ^ to \. Since ubuntu-latest uses Bash, the Windows-style ^ will cause the workflow to fail.

@chikle9090

chikle9090 commented Dec 13, 2025

Copy link
Copy Markdown
Collaborator Author

Hi, thanks for pointing that out!
I’ve already updated the workflow to replace the Windows-style ^ with Bash-compatible , and the action is now passing on ubuntu-latest.
Please let me know if you’d like any further changes. @Santosh69

@Santosh69

Santosh69 commented Dec 13, 2025

Copy link
Copy Markdown
Collaborator

Hi @chikle9090 , have you made the changes for? (lines 17-18)

you change the line breaks from ^ to \

@chikle9090

chikle9090 commented Dec 13, 2025

Copy link
Copy Markdown
Collaborator Author

Yes — lines 16–17 have been updated to use Bash-style \ instead of ^.
The workflow now runs successfully on ubuntu-latest. @Santosh69

@Santosh69

Copy link
Copy Markdown
Collaborator

Hi @latishab , @tqmsh, whenever you have time, please review this PR

@mohi-devhub mohi-devhub left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Found a few things to address:

  • The curl command should explicitly specify -X POST.

  • The notification content is very minimal , consider including event name, repo, actor, and a relevant link.

  • There’s no error handling for failed webhook requests.

  • The workflow triggers on all pushes/PRs/issues, which could lead to Discord spam , consider narrowing triggers or adding conditions.

As an alternative, you could also use an existing action like sarisia/actions-status-discord, which handles formatting and edge cases out of the box.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Integrate OmniParser & Optimize Model Loading

3 participants