Moved Style/SingleArgumentDig into separate TODO file

@anshulriyal

Thank you for your contribution to GitLab. We believe that everyone can contribute and contributions like yours are what make GitLab great!

Our Merge Request Coaches will ensure your contribution is reviewed in a timely manner*.
If you haven't, please set up a DANGER_GITLAB_API_TOKEN.
You can comment @gitlab-bot label ~"group::<group name>" to add a group label or @gitlab-bot label ~"type::<type name>" to add a type label.
If you need help moving the MR forward or finding a reviewer, feel free to ask @gitlab-bot help or ping a Merge Request Coach.
Read more on how to get help.
You can provide feedback on the GitLab Contributor Experience in this survey

This message was generated automatically. You're welcome to improve it.

added Community contribution label

assigned to @anshulriyal

This merge request will be considered part of the quarterly GitLab Hackathon for a chance to win a prize.

Can you make sure this merge request mentions or links to the relevant issue that it's attempting to close?

Thank you for your contribution!

added Hackathon label

mentioned in issue #354328 (closed)

added Engineering Productivity backend static code analysis typemaintenance labels

changed milestone to %15.0

requested review from @splattael

approved this merge request

Thanks @anshulriyal

Looks good to me

Rebased against latest master.

@splattael, thanks for approving this merge request.

This is the first time the merge request is approved. To ensure full test coverage, please start a new pipeline before merging.

For more info, please refer to the following links:

resolved all threads

added 1125 commits

4ab9b506...e400b448 - 1124 commits from branch gitlab-org:master
b9480196 - Moved Style/SingleArgumentDig into separate TODO file

Compare with previous version

Suggested Reviewers (beta)

This is an experimental ML-based code reviewer recommendation system created by ~"group::applied ml".

The individuals below may be good candidates to participate in the review based on various factors.

After you review all recommendations, please assign reviewers manually, as this is not done automatically.

You can use slash commands in comments to quickly assign /assign_reviewer @user1.

Reviewers
`@kushalpandya`, `@DouweM`, `@rspeicher`, `@rymai`, `@iamphill`

If you do not believe these recommendations are useful or if you do not want to use any of the suggestions, please apply the label Bad Suggested Reviewer. You can also provide feedback for this feature on this issue: https://gitlab.com/gitlab-org/gitlab/-/issues/357923.

Automatically generated by Suggested Reviewers Bot

enabled an automatic merge when the pipeline for 2937c4ba succeeds

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	Huzaifa Iftikhar (`@huzaifaiftikhar1`) (UTC+5.5)	Luke Duncalfe (`@.luke`) (UTC+12)

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.

Generated by Danger

added Bad Suggested Reviewer label

merged

@anshulriyal, how was your code review experience with this merge request? Please tell us how we can continue to iterate and improve:

Leave a or a on this comment to describe your experience.
Create a new comment starting with @gitlab-bot feedback below, and leave any additional feedback you have for us in the comment.

Have five minutes? Take our survey to give us even more feedback on how GitLab can improve the contributor experience.

Thanks for your help!