Proposal: Rename broken master incident labels to scoped labels
Goal
Simplify the process of labeling broken master incidents, so we don't have to manually remove ~"master-broken:undetermined" when applying a concrete root cause label. This is to ensure that we don't accidentally leave ~"master-broken:undetermined" which will affect the accuracy of our dashboards. It was my fault since I went ahead and created these non-scoped labels without considering the inconvenience it will cause us.
Proposal
Rename the following labels to scoped, so changing :
to ::
, which allows auto removing ~"master-broken:undetermined" when a new label is added.
- ~"master-broken:caching"
- ~"master-broken:ci-config"
- ~"master-broken:dependency-upgrade"
- ~"master-broken:flaky-test"
- ~"master-broken:fork-repo-test-gap"
- ~"master-broken:infrastructure"
- ~"master-broken:pipeline-skipped-before-merge"
- ~"master-broken:test-selection-gap"
- ~"master-broken:undetermined"
- ~"master-broken:need-merge-train"
In addition to renaming the labels, the following code changes are also required:
- master broken incident dashboard
- master broken root cause analysis Sisense chart
- docs describing master broken labels (cannot find the link, maybe we never added them to any doc, I will do that in this issue too.)
WDYT @gl-quality/eng-prod any concern with this proposal?
Edited by Jennifer Li