Filter /github subscribe release notifications by prerelease status
#200548
Replies: 1 comment
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Apps
Body
Summary — The GitHub for Slack integration (
/github subscribe owner/repo releases) sends a Slack message for every published release, with no way to distinguish full releases from pre-releases.Problem — Many CD pipelines publish a pre-release (
prerelease: true) on stage deploys and a full release (prerelease: false) on prod promotion. Thereleasessubscription fires on thepublishedevent regardless of theprereleaseflag, so channels get pinged on every stage deploy — drowning the production-release signal teams actually want.Requested behavior — A prerelease filter mirroring the existing
workflows:{event,branch}filter syntax:(The
prerelease:falsequalifier already exists in GitHub's release search UI — just not for Slack.)Related — #178699 (same request class, for PRs); native-notification equivalents #4993, #29192, #10776, #17052.
Beta Was this translation helpful? Give feedback.
All reactions