chore: post slack message on staging-internal deploy failures#24146
Open
AztecBot wants to merge 1 commit into
Open
chore: post slack message on staging-internal deploy failures#24146AztecBot wants to merge 1 commit into
AztecBot wants to merge 1 commit into
Conversation
AztecBot
added
ci-draft
alexghr
approved these changes
Jun 17, 2026
alexghr
changed the title
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
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.
What
The reusable
deploy-network.ymlworkflow derives its failure-alert Slack channel as#alerts-<network>, so failedstaging-internaldeploys currently post to#alerts-staging-internal. This adds an override sostaging-internaldeploy failures route to#alerts-staging-publicinstead.Detail
The override is scoped to
inputs.network == "staging-internal"only, so every other network keeps its existing#alerts-<network>destination. The downstreamCHANNEL_IDused for the Slack permalink and the ClaudeBox investigation dispatch (slack_channel/slack_thread_ts) is read from thechat.postMessageresponse, so the ClaudeBox investigation thread follows the new channel automatically with no further change.The deploy bot's
SLACK_BOT_TOKENmust be a member of#alerts-staging-publicfor the post to land.Requested by Alex Gherghisan.
Created by claudebox · group:
slackbot