A team using "GitHub Actions" wants every member who is watching a repository to be notified when a scheduled nightly workflow run fails, without standing up any external monitoring service or webhook receiver. Which native mechanism delivers these failure notifications?
- AAn Azure Monitor activity log alert scoped to the repository's workflow, paired with an action group, which emails the watchers whenever the nightly GitHub Actions workflow run reports a failed status.
- BA repository webhook delivering workflow run events to a self-hosted receiver that parses the payload and forwards a message to the watchers whenever a nightly workflow run finishes with a failure.
- CA branch protection rule requiring the nightly workflow as a status check, so a failed run blocks merges and the resulting check failure message informs the watchers that the nightly run did not succeed.
- DGitHub's built-in Actions notifications, which send the watchers their configured email or web notification when a workflow run they are subscribed to fails, with no external service required. Correct
Why A is wrong: Azure Monitor activity log alerts watch Azure resource operations and is tempting because it does alerting, but it has no visibility into GitHub Actions run status, so it cannot fire on the failure.
Why B is wrong: A webhook plus self-hosted receiver can detect failures but requires standing up and maintaining an external service, which directly violates the requirement to avoid any external receiver.
Why C is wrong: Branch protection status checks gate pull request merges, and a scheduled nightly run is not tied to a merge, so the rule neither evaluates that run nor notifies watchers of its failure.
Why D is correct: GitHub natively notifies users about Actions workflow run failures through their existing notification settings, delivering the failure alerts without any external monitoring service or webhook receiver.