Use ref instead of sha for CI config variables
What does this MR do?
Fixes a minor bug introduced in !66852 (merged)
A SHA cannot be used as a ref for variable expension. The ref is meant to be a branch name or a tag name, and it is used to decide if the branch or tag is protected. Passing a sha results in the ref getting treated as unprotected, unless the sha happens to match a protected branch or tag (which is a security issue).
See #337344 (closed)
Screenshots or Screencasts (strongly suggested)
How to setup and validate locally (strongly suggested)
Does this MR meet the acceptance criteria?
Conformity
-
I have included changelog trailers, or none are needed. (Does this MR need a changelog?) - No entry because this fixes a regression introduced during the current milestone
-
I have added/updated documentation, or it's not needed. (Is documentation required?) -
I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?) -
I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?) -
I have self-reviewed this MR per code review guidelines. -
This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines) -
I have followed the style guides. -
This change is backwards compatible across updates, or this does not apply.
Availability and Testing
-
I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.) -
I have tested this MR in all supported browsers, or it's not needed. -
I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.
Edited by Hordur Freyr Yngvason