[Akiyo974]

GitHub usernames are case-insensitive (github.com/nunomaduro and github.com/NunoMaduro are the same profile), but /dev/null looked them up exactly. A profile link typed or shared in another case was a 404, on every {user:username} route:

• https://dev-null.sh/@NunoMaduro → 404 (https://dev-null.sh/@nunomaduro works)
• https://dev-null.sh/api/v1/users/NunoMaduro → 404
• the same for /commits/{commit}, /followers, /following, /feed.atom, /og.png…

User::resolveRouteBindingQuery() now matches username on LOWER(username), which the existing users_lower_username_index covers, so every route bound by username accepts any case. Usernames are already treated as unique case-insensitively (UpdateStaleUsernames, mentions), so at most one user can match. Other route keys are unchanged.

Tests: a profile and a commit page, and the public API, found in other cases. Both fail without the fix.

[Copilot]

🟢 Approval recommended

The change is narrowly scoped, preserves other bindings, and includes targeted regression coverage with no unresolved findings.

No open issues 🎉

What changed in this PR

Makes username-bound routes case-insensitive, matching GitHub’s behavior and preventing case-related 404s.

Changes:

• Adds case-insensitive username binding while preserving other route keys.
• Adds regression coverage for profile, commit, and public API requests.

File	Description
tests/​Feature/​Controllers/​UserControllerTest.php	Tests profile and commit access with alternate username casing.
tests/​Feature/​Controllers/​Api/​UserControllerTest.php	Tests case-insensitive public API lookup.
app/​Models/​User.php	Overrides username route binding with a lowercase comparison.

_{Review effort: Balanced}

[Copilot]

🟢 Approval recommended

The focused change preserves other bindings, includes relevant regression coverage, and has no identified blocking issues.

No open issues 🎉

_{Review effort: Balanced}

[jubianchi]

Hi @Akiyo974, thanks for this one. I think production now finds handles in any case, through #1286 (Oct 29) and #1338 (Oct 31), on top of the move of handles to profiles in #1156:

• User::resolveRouteBindingQuery() resolves {user:handle} through Profile, and profiles.handle is now citext
• https://dev-null.sh/@NunoMaduro answers a 301 to /@nunomaduro, and /api/v1/users/NunoMaduro answers 200
• tests cover it in tests/Unit/Models/ProfileTest.php and in the UserControllerTest / CommitControllerTest "in its own case" cases

The users.username column this PR matches on was dropped in #1156. As far as I can tell, what this PR fixes is covered there.