Skip to content

Add a new file to test

Evan Read requested to merge eread/explicitly-add-new-file-to-test into master

What does this MR do and why?

When rebasing a branch for !146594 (merged) against master, I notice I had a new broken test: https://gitlab.com/gitlab-org/gitlab/-/jobs/6442931351.

That seems to be caused by introducing a new file in !147169 (merged) without accounting for it in pipeline configuration (or excluding it from the test).

This MR excludes it from the test because I don't think we want to test changes to the file?

CC @jachapman @ntepluhina

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

Merge request reports