Gitlab CODEOWNERS with custom groups doesn't parse

[joshdales]

Environment

SaaS (https://sentry.io/)

Steps to Reproduce

Import a Gitlab CODEOWERS from connected repo that has named sections with a default owner that maps to mapped teams. eg. we have something that looks something like this:

[Team Core] @org/team-core
folder-1/

[Team Other] @org/team-other
folder-2/

Expected Result

Should parse the CODEOWNERS file and rules correctly, and assign the code that it is owned to the correct team or person.
The documentation about this syntax is here: https://docs.gitlab.com/user/project/codeowners/reference/#set-default-code-owner-for-a-section

Actual Result

Got an error banner that reads

There was 1 ownership issue within Sentry on the latest sync with the CODEOWNERS file

The following usernames do not have an association in the organization: org-name
Core]

And there is a new codeowner entry in the ownership table called [Team

Product Area

Settings - Projects

Link

https://{ORG_SLUG}.sentry.io/settings/projects/{PROJECT_SLUG}/ownership/

DSN

https://42a75d0589aa4085b0a6b61a48f8bead@o1301086.ingest.sentry.io/6570851

Version

No response

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-settings-integrations for triage ⏲️

[getsantry]

Routing to @getsentry/product-owners-issues for triage ⏲️

[sentaur-athena]

Rerouting to issues because it seems like a codeowner parsing problem.

[JoshFerge]

Hello, thank you for the issue. It looks like Gitlab's CODEOWNER syntax has some features that github's doesn't, and Sentry only supports Github's syntax at the moment. let me work with the team internally to prioritize. thanks!