Case closed for GitHub handles
Type a handle in lowercase and it still finds the person or organization, spelled the way GitHub spells it. The database now keeps one profile per handle, whatever its capitalization.
Top storyFirst on the front page. Held off 6 challengers since.
You are adding people to a new org and type a co-maintainer's handle in lowercase, though GitHub spells it with a capital. It lands, listed in the order you typed. No not-found, no wrong profile, no retyping.
Credit goes to mnapoli, who moved the case rule out of a pile of hand-written lookups and into the database. Handles now sit in a column that compares without regard to case, and one unique rule keeps each handle to a single profile, person or organization. That covers profile pages, mentions, organization pages through the API, following an organization, and search rankings. Adding members accepts up to 99 handles and spots the same person written two ways.
One catch. The upgrade merges nothing. If your database already holds @laravel and @Laravel as two profiles, the new unique rule refuses one of them and the upgrade stops rather than picking a winner.
Key files · #1338
- database/
migrations/ 2026_10_31_120000_make_profile_handles_case_insensitive.php - app/
Models/ Profile.php - app/
Models/ User.php - app/
Http/ ShowOrganizationRequest.phpRequests/ - app/
Http/ ShowApiOrganizationRequest.phpRequests/ - app/
Http/ CreateOrgRequest.phpRequests/ - app/
Http/ CreateOrgMemberRequest.phpRequests/ - app/
Queries/ UserSearchQuery.php