[QUARANTINE] Create Protected branch support when developers and maintai
requested to merge 1-quarantine-d26253bf-Create-Protected-branch-support-when-developers-and-maintainers-are-not-allowed-to-push-to-a-protected-branch-user-without-push-rights-fails-to-push into master
What does this MR do?
Quarantines the test Create Protected branch support when developers and maintainers are not allowed to push to a protected branch user without push rights fails to push
This test was identified in the reliable e2e test report:
Testcase: https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/347757
E2E Test Failure issue(s)
https://gitlab.com/sliaquat/gitlab/-/issues/1
Check-list
-
General code guidelines check-list -
Quarantine test check-list -
Follow the Quarantining Tests guide. -
Confirm the test has a quarantine:
tag with the specified quarantine type. -
Note if the test should be quarantined for a specific environment. -
(Optionally) In case of an emergency (e.g. blocked deployments), consider adding labels to pick into auto-deploy (Pick into auto-deploy priority1 severity1).
-
-
To ensure a faster turnaround, ask in the #quality_maintainers
Slack channel for someone to review and merge the merge request, rather than assigning it directly.
(This MR was automatically generated by
gitlab_quality-test_tooling
at 2024-02-27 11:58:19 UTC)