Stop running secret_detection for trains
@steveazz I was googling for examples to avoid some jobs in merge train, and found your commit. Unfortunately, merge trains seem to be merge requests too, so $CI_MERGE_REQUEST_IID
will be true and evaluated before.
Examples of merge train with failing secret detection:
- https://gitlab.com/gitlab-org/release-cli/-/pipelines/408664172
- https://gitlab.com/gitlab-org/release-cli/-/pipelines/408656928
Sometimes it's working, but I think it's flaky because it depends when we squash commits. Anyway, since your initial idea was to avoid running the job, I think this is way to do it correctly. Please let me know your thoughts. Thanks