github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-24 08:01:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #2866] [MERGED] chore: fix discord release message workflow #30134

New Issue
Closed
opened 2026-04-17 21:19:16 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-17 21:19:16 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/2866
Author: @BlankParticle
Created: 6/1/2025
Status: ✅ Merged
Merged: 6/1/2025
Merged by: @Bekacru

Base: main ← Head: chore/ci/fix-discord-workflow

📝 Commits (1)

  • 68ab1b8 chore: fix discord release message workflow

📊 Changes

2 files changed (+15 additions, -26 deletions)

View changed files

➖ .github/workflows/discord.yml (+0 -25)
📝 .github/workflows/release.yml (+15 -1)

📄 Description

I noticed that the Send to discord workflow never ran once,
after some digging I found that the github releases are done by github-actions and it can't trigger another action based on that event due to safety measures, so that recursive workflows doesn't trigger.

So I moved the discord workflow into the release flow, so If there is a WEBHOOK_URL set it should just start working as expected and send better releases to better auth discord than the current boring ones

Important

make sure to setup WEBHOOK_URL secret from discord webhook if not done already

🔄 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/better-auth/better-auth/pull/2866 **Author:** [@BlankParticle](https://github.com/BlankParticle) **Created:** 6/1/2025 **Status:** ✅ Merged **Merged:** 6/1/2025 **Merged by:** [@Bekacru](https://github.com/Bekacru) **Base:** `main` ← **Head:** `chore/ci/fix-discord-workflow` --- ### 📝 Commits (1) - [`68ab1b8`](https://github.com/better-auth/better-auth/commit/68ab1b8ca2993bbf5747ac9c04d1ce1330fcb0a3) chore: fix discord release message workflow ### 📊 Changes **2 files changed** (+15 additions, -26 deletions) <details> <summary>View changed files</summary> ➖ `.github/workflows/discord.yml` (+0 -25) 📝 `.github/workflows/release.yml` (+15 -1) </details> ### 📄 Description I noticed that the Send to discord workflow never ran once, after some digging I found that the github releases are done by github-actions and it can't trigger another action based on that event due to safety measures, so that recursive workflows doesn't trigger. So I moved the discord workflow into the release flow, so If there is a `WEBHOOK_URL` set it should just start working as expected and send better releases to better auth discord than the current boring ones > [!IMPORTANT] > make sure to setup `WEBHOOK_URL` secret from discord webhook if not done already --- <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-04-17 21:19:16 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#30134
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?