Read the Docs and GitHub Webhook Integration: Build Failure Notification Granularity

Read the Docs integrates with GitHub via webhooks to automate documentation builds upon commits to tracked branches. While the platform allows maintainers to enable build failure notifications via email, the current configuration options apply broadly to the project's build status.

In environments with multiple tracked versions—such as a stable production branch and several active development branches—a high volume of commits to unstable branches can generate significant notification noise. This makes it difficult to distinguish between a critical failure on the stable version and a routine build error on a feature branch.

Is it possible to configure notification alerts to trigger only for specific tracked branches? If global settings are the only option, what is the recommended approach to isolate critical stable-build alerts from development noise?