GQL code owners Validation for every file named CODEOWNERS

What does this MR do and why?

GQL code owners Validation for every file named CODEOWNERS

Changelog: added EE: true

See #216066 (comment 1468152154)

Screenshots or screen recordings

    query {
      project(fullPath: PROJECT_FULL_PATH) {
        repository {
          validateCodeownerFile(ref: REF, path: BLOB_PATH) { # nil if the BLOB_PATH file name is not 'CODEOWNERS' or does not exists
            total
            validationErrors {
              code
              lines
            }
          }
        }        
      }
    }

Related to #415352 (closed)

changed milestone to %16.2

added Category:Source Code Management CodeOwners Deliverable GitLab Free GitLab Premium GitLab Ultimate backend devopscreate documentation featureaddition groupsource code quad-planningcomplete-action sectiondev typefeature workflowin review labels

assigned to @jpcyiza

added GraphQL label

removed workflowin review label

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/api/graphql/reference/index.md (Link to current live version)

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

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	Hitesh Raghuvanshi (@hraghuvanshi) (UTC+5.5, 3.5 hours ahead of @jpcyiza)	Terri Chu (@terrichu) (UTC-4, 6 hours behind @jpcyiza)

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

Hey @imand3r, could you give this MR its initial review?

requested review from @imand3r

Allure report

allure-report-publisher generated test report!

e2e-test-on-gdk: test report for dada2a35

expand test summary

+------------------------------------------------------------------+
|                          suites summary                          |
+-------------+--------+--------+---------+-------+-------+--------+
|             | passed | failed | skipped | flaky | total | result |
+-------------+--------+--------+---------+-------+-------+--------+
| Plan        | 47     | 0      | 0       | 40    | 47    | ❗     |
| Create      | 27     | 0      | 1       | 20    | 28    | ❗     |
| Govern      | 19     | 0      | 0       | 18    | 19    | ❗     |
| Data Stores | 20     | 0      | 0       | 15    | 20    | ❗     |
| Manage      | 12     | 0      | 1       | 12    | 13    | ❗     |
| Verify      | 8      | 0      | 0       | 8     | 8     | ❗     |
+-------------+--------+--------+---------+-------+-------+--------+
| Total       | 133    | 0      | 2       | 113   | 135   | ❗     |
+-------------+--------+--------+---------+-------+-------+--------+

approved this merge request

@imand3r, thanks for approving this merge request.

This is the first time the merge request is approved. To ensure full test coverage, a new pipeline will be started shortly.

For more info, please refer to the following links:

• rspec predictive jobs
• jest predictive jobs
• merging a merge request.

added pipeline:mr-approved label

requested review from @garyh

added 1 commit

• a94dcec9 - GQL code owners Validation for every file named CODEOWNERS

Compare with previous version

changed the description

Hey @vyaklushin could you give this MR a maintainer look, please?