[Improve] Remove Slack prerequisite from Automations - #975
Merged
Conversation
Contributor
mrubens
marked this pull request as ready for review
August 1, 2026 19:58
mrubens
requested review from
brunobergher,
daniel-lxs and
mrubens
as code owners
August 1, 2026 19:58
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
1 participant
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.
What changed
Removed the generic Slack connection banner from the Automations settings page. The targeted reconnect warning for Slack installations missing required permissions remains unchanged.
Why this change was made
Automations support multiple communication providers, so presenting Slack as a general prerequisite is misleading.
Impact
Users can browse and configure Automations without seeing a Slack-specific prerequisite banner. Provider-specific configuration and permission guidance still appears where relevant.
Screenshots