ranade-oss makes protected check failures harder to miss
A failed protected check now leaves a clear, safe trail in the pull request instead of quietly ending its run.
When an automated check cannot safely repair a protected failure, ranade-oss now adds one concise pull-request comment after the run finishes. It points reviewers to the completed run and names the jobs and steps that failed.
The guardrails matter as much as the alert: the comment does not reveal logs or secrets, and it does not restart work that has already completed. Repeated runs also will not pile duplicate notices onto the same pull request.
So what Legal-tech teams relying on controlled automation should care because exceptions become visible to reviewers without giving the automation extra power to change protected work.
Spotted something wrong? Or know the PR text has fresher detail than the writeup above?