-
Notifications
You must be signed in to change notification settings - Fork 2
Repository Notifications
Official EasyLibrary repositories use GitHub Actions for Discord notifications. Manual GitHub Settings Webhooks should not be used for push, release or changelog notifications.
Required files:
.github/scripts/notify-discord.py
.github/workflows/repository-notifications.yml
.github/workflows/release.yml
release.yml only applies to repositories that publish release assets.
Required secrets:
DISCORD_PUSH_WEBHOOK_URL
DISCORD_RELEASE_WEBHOOK_URL
If a secret is missing, the workflow skips the notification safely. Notification failure should not fail quality, build or release jobs.
The repository notification workflow supports workflow_dispatch, which sends
a manual test payload to the push notification channel.
Release notifications are sent from the release workflow after assets are
published and verified. They do not rely on a separate on: release workflow.
The shared Discord embed keeps author icons, clickable repository/branch/tag links, commit/release links and compact fields. Webhook URLs are never printed.
- Package Manager
- Package Backed Plugins
- Standalone vs Package
- Package Switch and Migration
- Package Doctor
- Package Safety Gate
- Support Report Bundle
- Timings
- Package Recovery
- Proxy Troubleshooting
- Migrating from EasyLibrary 2.0 to 3.x
- Embedded Libraries Migration Map
- Removed Features and Replacements
- Deprecated APIs
- Compatibility Policy
- Config Migration
- Plugin Developer Migration
- Server Administrator Migration
- Official Libraries
- LibPacket
- LibCommand
- LibSerializer
- LibForm
- LibDB
- LibCommons
- LibHttp
- LibAssets
- LibPlaceholder
- LibWorld
- EasyLibrary Agent Bridge
- LibCustom
- LibEnchantment
- LibHud
- LibTrigger
- LibWindow
- Public API Contract
- Doctor Output
- Repository Notifications
- Smoke Tests
- Common Errors
- Release and Changelog