Limit amount of triggers for qa gem cache update jobs
What does this MR do and why?
It seems default-refs
cover too many cases (name is a bit deceiving imo) which causes renovate forked pipelines (example: https://gitlab.com/gitlab-renovate-forks/gitlab/-/pipelines/1082832706) to get stuck because the fork has no access to e2e
runner. Limit amount of triggers to actual refs that could receive Gemfile.lock
update
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.
Edited by Andrejs Cunskis