Skip to content

Revert notification rerouting from #38 - #39

Merged
Aias00 merged 1 commit into
apache:masterfrom
cloudbase-ai:fix/revert-notification-rerouting-20261119
Nov 19, 2026
Merged

Aias00 merged 1 commit into
apache:masterfrom
cloudbase-ai:fix/revert-notification-rerouting-20261119

Conversation

@cloudbase-ai

Copy link
Copy Markdown
Contributor

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.

Signed-off-by: cloudbase-ai <22498243+cloudbase-ai@users.noreply.github.com>

@Aias00 Aias00 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

@Aias00
Aias00 merged commit d93d61a into apache:master Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants