Skip to content

Fix case sensitivity in CODEOWNERS validation

What is the problem?

Currently, CODEOWNERS validation incorrectly rejects valid usernames and group names when the case doesn't exactly match. For example, @REPORTED_user_21 would be rejected even if the user exists as @reported_user_21 in GitLab's database.

This creates confusion for users who expect case-insensitive matching, similar to how GitLab handles usernames and group paths elsewhere in the application.

Related to: CODEOWNERS Syntax Check is Case Sensitive, Appr... (#553323 - closed)

What does this MR do?

Fixes case sensitivity issues in CODEOWNERS validation by making username and group name matching case-insensitive.

Screenshots or screen recordings

Actual usernames in GitLab: @reported_user_21, @TestUser, group path: @codeowner-test1
Before: @REPORTED_user_21 returns a syntax error After: @REPORTED_user_21, @testUser, @Codeowner-TEST1 all passed
Screenshot_2025-08-02_at_12.40.17_am Screenshot_2025-08-02_at_12.43.12_am

How to set up and validate locally

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Emma Park

Merge request reports

Loading