Do not use attributes_for in RemoveDuplicateCsFindings spec

changed milestone to %Backlog

added Category:Vulnerability Management [deprecated] Accepting merge requests database devopssecure groupthreat insights maintenancerefactor sectionsec typefeature typemaintenance labels

added databasereview pending label

added backend label

	1 Warning
	This merge request does not have any assignee yet. Setting an assignee clarifies who needs to take action on the merge request at any given time.

2 Messages

This merge request adds or changes files that require a review from the Database team.

CHANGELOG missing:

If you want to create a changelog entry for GitLab FOSS, run the following:

bin/changelog -m 52497 "Do not use attributes_for in RemoveDuplicateCsFindings spec"

If you want to create a changelog entry for GitLab EE, run the following instead:

bin/changelog --ee -m 52497 "Do not use attributes_for in RemoveDuplicateCsFindings spec"

If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

This merge request requires a database review. To make sure these changes are reviewed, take the following steps:

Ensure the merge request has database and databasereview pending labels. If the merge request modifies database files, Danger will do this for you.
Prepare your MR for database review according to the docs.
Assign and mention the database reviewer suggested by Reviewer Roulette.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.

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, mention them as you normally would! Danger does not automatically notify them for you.

Category	Reviewer	Maintainer
backend	Nicolas Dular (`@nicolasdular`) (UTC+1)	Michael Kozono (`@mkozono`) (UTC-8)
database	Marius Bobin (`@mbobin`) (UTC+2)	Adam Hegyi (`@ahegyi`) (UTC+1)