Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pretty-prints GitHub Release webhooks inside Discord #8

Merged
merged 6 commits into from
Oct 7, 2024
Merged

Conversation

ViMaSter
Copy link
Member

@ViMaSter ViMaSter commented Oct 5, 2024

Summary

Discords GitHub Webhook handling is… fine.
I've updated it to not just show the new version number, but changelog and direct links to the download as well.

Instead of going

GitHub --Webhook--> Discord

we now go

GitHub --Webhook--> Website --Webhook--> Discord

and the added endpoint /webhook takes care of converting release.published messages to Discord embeds and forwarding that to Discord.

Added a test for the conversion as well.

(For some reason we were running Node.js 20 but the package.json wasn't up to date; remedied that.)

Before/after screenshots and/or animated gif

Before

image

After

image

Testing instructions

Push a commit prefixed with feat:, fix:, feat!: or fix!: to the game repository's default branch and that message should make it's way to Discord.

Additional information

  • [ ] Changes UI
  • [ ] Has associated resource:

Copy link
Member

@lyndsiWilliams lyndsiWilliams left a comment

Choose a reason for hiding this comment

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

The code looks good on this, I'ma trust-approve it! We can "test in prod" with the next PR and if it explodes we can just revert it 🔥

@ViMaSter ViMaSter merged commit 1306521 into main Oct 7, 2024
3 checks passed
@ViMaSter ViMaSter deleted the webhooks branch October 7, 2024 19:41
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.

2 participants