Match the file list impacting assets

changed milestone to %15.11

added Engineering Productivity maintenancepipelines labels

assigned to @godfat-gitlab

added typemaintenance label

added backend label

Pipeline Changes

This merge request contains changes to the pipeline configuration for the GitLab project.

Please consider the effect of the changes in this merge request on the following:

Effects on different pipeline types
Effects on non-canonical projects:
- gitlab-foss
- security
- dev
- personal forks
Effects on pipeline performance

Please consider communicating these changes to the broader team following the communication guideline for pipeline changes

Reviewer roulette

Changes that require review have been detected!

Please refer to the table below for assigning reviewers and maintainers suggested by Danger in the specified category:

Category	Reviewer	Maintainer
backend	Pedro Pombeiro (`@pedropombeiro`) (UTC+2, 6 hours behind `@godfat-gitlab`)	Thong Kuah (`@tkuah`) (UTC+13, 5 hours ahead of `@godfat-gitlab`)
maintenanceworkflow / maintenancepipelines for CI, Danger	Ravi Kumar (`@rkumar555`) (UTC+2, 6 hours behind `@godfat-gitlab`)	Rémy Coutable (`@rymai`) (UTC+2, 6 hours behind `@godfat-gitlab`)
Engineering Productivity	Reviewer review is optional for Engineering Productivity	Ash McKenzie (`@ashmckenzie`) (UTC+11, 3 hours ahead of `@godfat-gitlab`)

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

@ddieulivol Please review? Thank you! /cc @leipert

@godfat-gitlab Looks good to me, thanks!

@godfat-gitlab / @ddieulivol Wonder if we should parse the rules from the yaml :see_no_evil:

@leipert I think that'll be fine. I took a quick check, the only thing which is more complex is probably that we need to make sure we respect FOSS_ONLY, so that when ::Gitlab.ee? is false, it did not include files under ee/ even if the directory does exist with tons of files under it. The same goes to ::Gitlab.jh?. This means we would have a special case for "{,ee/,jh/}app/assets/**/*".

I don't have anything other than "if it's not breaking, don't touch it" to say :P So sure if it's working I think.