Update Slack notification to use official shared action - #114
Merged
Conversation
lcjohnso
approved these changes
Jun 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🪦 https://github.com/8398a7/action-slack 🪦
RIP Action Slack.
This migrates the slack notification shared workflow to the official Slack Github Action. It still takes a very similar payload, so minimal changes were required outside of needing to do the status if/else in bash instead of JS. This also means no updates of any downstream workflows are necessary, it uses all the same inputs.
I also added an option to pick a channel (still defaults to #deploys) and a new test action that will run as a merge requirement or a workflow dispatch (sends to #slack-test).
edit: Test runs and posts correctly to #slack-test, can't test it via workflow_dispatch until this merges. I'll merge soon and watch new deploys for issues.