-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Add GitHub webhook for auto-labeling of sponsor issues #299
Conversation
🧪 Details on macOS Unix 14.6.1✅ Devlooped.Tests.SponsorLinkTests.TryRead 🧪 Details on Ubuntu 22.04.4 LTS✅ Devlooped.Tests.SponsorLinkTests.TryRead 🧪 Details on Microsoft Windows 10.0.20348✅ Devlooped.Tests.SponsorLinkTests.TryRead from dotnet-retest v0.6.1 on .NET 8.0.7 with 💜 |
Auto-labeling works by configuring a webhook (at repo or organization level). The optional `GitHub:Secret` configration can be used to secure the webhook callback, but it's not required (although recommended). The endpoint is `github/webhooks` and should be set to receive `application/json` content type. Currently, the webhook callback only processes sponsorship changes (to refresh the cached list of sponsors), issues and issue comments. Issue actions result in auto-labeling. Labels for sponsors of certain tiers can be configured via yaml metadata in the tier description, like: ``` ☕ You want to buy me a Nespresso capsule, and everyone should be allowed to do that 🤗 <!-- tier: basic label: sponsor 💜 color: #D4C5F9 --> ``` Tiers inherit metadata from lower tiers so you don't have to repeat them. Also optionally introduce pushover-based notifications (for issue and issue comment actions), if the following secrets are configured: - `PushOver:Token`: the API key/token - `PushOver:Key`: the user or delivery group key See https://pushover.net/api for more info on that.
Auto-labeling works by configuring a webhook (at repo or organization level). The optional
GitHub:Secret
configration can be used to secure the webhook callback, but it's not required (although recommended). The endpoint isgithub/webhooks
and should be set to receiveapplication/json
content type.Currently, the webhook callback only processes sponsorship changes (to refresh the cached list of sponsors), issues and issue comments. Issue actions result in auto-labeling.
Labels for sponsors of certain tiers can be configured via yaml metadata in the tier description, like:
Tiers inherit metadata from lower tiers so you don't have to repeat them.
Also optionally introduce pushover-based notifications (for issue and issue comment actions), if the following secrets are configured:
PushOver:Token
: the API key/tokenPushOver:Key
: the user or delivery group keySee https://pushover.net/api for more info on that.