Repository navigation
ci: limit Discord notifications to ARK and arknet - #1
Merged
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
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.
Discord Actions notifications are enabled only for ARK and arknet. Their caller workflows still use this repository's shared implementation and the organization-level DISCORD_WEBHOOK_URL Secret.
Update the bilingual setup instructions and remove the bulk installer so future maintenance does not restore notification YAMLs across the organization. The other 33 caller files have been removed after matching their installed Git blob.
Validation: shared notification tests and actionlint; actual arknet message receipt matches the user-provided Webhook and its channel.