Forbid setting NO_ACCESS to unprotect-access-level for protected branches

mentioned in issue #345277 (closed)

@ghinfey, Please add a group or category label to identify issue ownership. You can refer to the Features by Group handbook page for guidance. If you are unsure about the correct group, please do not leave the issue without a group label. Please refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issue.

mentioned in merge request !112035 (merged)

This issue was automatically tagged with the label groupsource code by TanukiStan, a machine learning classification model, with a probability of 0.98.

If this label is incorrect, please tag this issue with the correct group label as well as automation:ml wrong to help TanukiStan learn from its mistakes.

If you are unsure about the correct group, please do not leave the issue without a group label. Please refer to GitLab's shared responsibility functionality guidelines for more information on how to triage this kind of issues.

Authors who do not have permission to update labels can leave the issue to be triaged by group leaders initially assigned by TanukiStan

This message was generated automatically. You're welcome to improve it.

added automation:ml groupsource code labels

added devopscreate sectiondev labels

added typebug label

added backend label

added Category:Source Code Management label

marked this issue as related to #345277 (closed)

Setting as priority2 severity2 as per the original issue.

added priority2 severity2 labels

Adding to %16.0 planning.

changed milestone to %16.0

added bugfunctional label

added workflowin review label

Hi @sean_carroll, I have an MR for this in review, I've added the label.

Amazing! Thank you @ghinfey

Adding this to %15.10

changed milestone to %15.10

mentioned in merge request !112869 (merged)

mentioned in issue gitlab-org/quality/triage-reports#11596 (closed)

@sean_carroll, @tlinz and @a_mcdonald,

This groupsource code bug has at most 50% of the SLO duration remaining and is an SLONear Miss breach. Please consider taking action before this becomes an SLOMissed in 29 days (2023-04-18).