Make sure we do not have blanket changes in CI rules
This is a follow up from !102881 (merged) to add a test to make sure we're not adding new blanket changes in CI rules.
Using blanket changes in CI rules often break specialized pipelines which might not be associating with a merge request, which changes
will always be evaluated as true
, therefore not accurate and dependent jobs often are not available.
See also: https://docs.gitlab.com/ee/development/pipelines/internals.html#avoid-force_gitlab_ci
The following discussion from !141850 (merged) should be addressed:
-
@rymai started a discussion: (+1 comment)
question: This breaks the case of docs-only pipelines. Did you mean?
- <<: *if-default-refs changes: *glfm-patterns