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

Notification for Promoting Pre-Releases to Latest Releases #1999

Open
mazlan25 opened this issue Jan 17, 2025 · 0 comments
Open

Notification for Promoting Pre-Releases to Latest Releases #1999

mazlan25 opened this issue Jan 17, 2025 · 0 comments

Comments

@mazlan25
Copy link

Is your feature request related to a problem?
Please describe.
Currently, the GitHub-Slack integration does not send notifications when a pre-release is promoted to a latest release. This creates a communication gap, as our team does not get notified when production deployments happen. Additionally, the integration does not allow us to customize the notification messages, which limits the ability to provide relevant context or format the notifications according to team preferences.

Describe the solution you'd like

  1. Notification for Promoting Pre-Releases to Latest Releases:
    • Add support for Slack notifications when a pre-release is promoted to a latest release.
    • Include the relevant details, such as release version, associated changes, and links to the release.
  2. Feature to Edit Notification Messages:
    • Allow customization of Slack notification messages, such as:
      • Modifying the message format.
      • Adding custom text or links.
      • Including specific tags or mentions for relevant team members.
      • Adding environment variables for deployment on different environment during pre-release and latest-release

Additional context
Our team uses GitHub-Slack integration extensively to track release updates, especially for automated CI/CD pipelines. Notifications for promoting pre-releases to production (latest release) are critical for ensuring everyone is aligned on production changes.
Example scenarios where this feature would be helpful:

  • Notifying the team about a production deployment triggered by promoting a pre-release.
  • Customizing messages to include specific instructions or tagging key team members for immediate follow-up or for stating which environment deployment was done.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant