Adds a rule to make gdk reliable suite as blocking for matching labels
What does this MR do and why?
Relates to gitlab-org/quality/quality-engineering/team-tasks#1848 (comment 1543069224).
So that we don't end up blocking all MRs if an E2E spec fails, going with a phased approach.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.