ci: drop Slack @here notification from schema-compat failure - #57
Merged
Conversation
Match django-paradedb: keep the auto-filed GitHub issue but stop paging Slack on every failed schema-compat run.
philippemnoel
requested review from
isaacvando,
mdashti,
rebasedming and
stuhood
as code owners
April 23, 2026 20:40
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.
Summary
Notify Slack on Failurestep from.github/workflows/schema-compat.ymlso failed schema-compat runs no longer page<!here>in Slack.django-paradedb, which only files a GitHub issue on failure. The auto-filed GitHub issue is preserved here.Test plan
repository_dispatch: paradedb-release(or a manualworkflow_dispatch) on this branch fails intentionally and only a GitHub issue is created — no Slack message.