fix SLACK_WEBHOOK_TYPE to lowercase in workflow files#94
Merged
Conversation
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.
Note
Low Risk
Cosmetic env value fix for Slack webhook configuration; no auth, secrets, or scan logic changes.
Overview
Updates
SLACK_WEBHOOK_TYPEfromINCOMING_WEBHOOKtoincoming-webhookeverywhere the pinnedslackapi/slack-github-actionstep posts Slack notifications.The change applies to failure alerts in onboard-new-repo, release announcements in publish-release, and security scan failures in security-scan. Payloads, webhooks, and action versions are unchanged—only the webhook type env value is normalized to lowercase.
Reviewed by Cursor Bugbot for commit 6e520b2. Bugbot is set up for automated code reviews on this repo. Configure here.