Reactive processor to nudge team members to add root cause label to broken master incidents
Part 1
When ~"master-broken:undetermined" is still present after a broken master incident is closed, we should ping team member to label the incident with a concrete root cause label to improve the accuracy of our dashboards.
Part 2
If an incident is identified to be caused by flaky specs, we should also nudge team member to add a concrete flaky spec root cause label, to improve data for flaky test root cause analysis. This can be a separate nudger if needed.
Edited by Jennifer Li