Repository navigation
Conversation
Signed-off-by: cloudbase-ai <22498243+cloudbase-ai@users.noreply.github.com>
Aias00
approved these changes
Nov 19, 2026
Aias00
left a comment
Contributor
There was a problem hiding this comment.
Validated as an exact reversal of the five routing lines from #38. The restored configuration matches the prior file byte-for-byte and parses as YAML; unrelated settings are unchanged. This rolls back the mistaken rerouting and does not represent a completed notification shutdown, which requires an Infra-side control.
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
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.
Revert the routing-only addition from #38. The user requested disabling issue/PR email notifications altogether, not redirecting them to a different list.
This removes exactly the four explicit event-recipient keys and their comment introduced by #38, restoring the prior configuration byte-for-byte. It does not claim that deleting routing keys disables notifications: ASF documents fallback to legacy/default recipients, and its current YAML feature provides no disable switch. A server-side GitBox/Infra change is required for the requested shutdown. Commit notification configuration and all GitHub settings are unchanged.
Validation: exact reversal of #38, YAML parsing, one-file diff and restored-content comparison. No synthetic notification event or test email is created.