chore: update .github/CODEOWNERS

[srikanthccv]

No description provided.

[request-info]

We would appreciate it if you could provide us with more info about this issue/pr!

[github-actions]

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

[ankitnayan]

Maybe we should introduce folder wise owners in backend otherwise all 5-6 folks will be added as reviewer in every backend PR

[prashant-shahi]

@ankitnayan Shouldn't the backend related PRs be relevant for backend team to take a look at?

Perhaps not for Makefile and .git*, however query-service and go.* should be okay backend team to look at.
And approve from their end to unblock the person.

[srikanthccv]

The folder approach is brittle. While some folders have specific logic, overall files are distributed over several folders containing various changes. And with the folder-wise assignment, when the owners make changes (usually the case), no one is assigned.

[srikanthccv]

Or I can remove the CODEOWNERS for query-serivce and let the PR authors select who they want to get reviews from. Let me know what you think.

[ankitnayan]

let the PR authors select who they want to get reviews from

this looks good to me

[srikanthccv]

Updated

[srikanthccv]

@ankitnayan merge this. Let the author of PR select the reviewers for a change.