[wp-meta] [Making WordPress.org] #8092: Usernames with spaces result in an invalid emails on build repo mirror

[Making WordPress.org]

#8092: Usernames with spaces result in an invalid emails on build repo mirror
-----------------------------+---------------------
 Reporter:  desrosj          |       Owner:  (none)
     Type:  defect (bug)     |      Status:  new
 Priority:  normal           |   Milestone:
Component:  Version Control  |  Resolution:
 Keywords:                   |
-----------------------------+---------------------

Comment (by dd32):

 It's correct in git://core.git.wordpress.org/

 (@bernhard-reiter Are you sure you don't want to update your profile with
 your name rather than the slugified version on
 https://profiles.wordpress.org/bernhard-reiter/ ?)

 {{{
 commit 07a63531cf40369facf4304c4f899f097456a610
 Author: bernhard-reiter <bernhard-reiter at git.wordpress.org>
 Date:   Mon Sep 22 09:32:34 2025 +0000

     Block Bindings: Add `block_bindings_supported_attributes` filter.

     Add a block-agnostic version of the
 `block_bindings_supported_attributes_{$block_type}` filter first
 introduced in [60611].

     This allows adding block bindings support for attributes of multiple
 different blocks in one go.

     Follow-up to [60611].
     Props bernhard-reiter.
     See #62090.
     Built from https://develop.svn.wordpress.org/trunk@60790


     git-svn-id: https://core.svn.wordpress.org/trunk@60126 1a063a9b-
 81f0-0310-95a4-ce76da25c4cd
 }}}

 Unfortunately github.com/WordPress/WordPress doesn't mirror the official
 git mirrors, but rather is a sync script running somewhere else which has
 no access to our database and the git author scripts, and importantly
 doesn't have the same commit hash history.

 What this means, is that the Authorship of the commits is taken from SVN,
 which uses user_login as the author identifier, whereas we're using
 `user_nicename` in the git mirrors.

 The options forward are threefold:
  1. Update the existing sync script to use a kinda-nicename-conversion
 `strtolower( str_replace( [' ', '.' ], '-', $name ) )`
  2. Bring the existing sync script in-house and use our `get-author.sh`
 script - This is not ideal as it would mean maintaining yet-another
 svn/git mirror
  3. Switch WordPress/WordPress to mirroring core.git.wordpress.org - Which
 would result in the commit hashes for everything changing, or being stuck-
 in-time (ie. `master` would cease to be being updated, and we'd push to a
 new branch `trunk`).

 I guess we're stuck using option 1 for now, at least until someone from
 systems wants to figure it out :) so.. @markjaquith FYI I guess?

 Hmm.. I guess if we wanted to use option two, we could create a `core-
 github.git.wordpress.org` mirror, which maintained the existing commit
 hashes, and then continue to push that to the existing location.. The
 different branch naming would be problematic though, likewise the tagged
 versions would conflict.

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/8092#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org