Setting sex required Edit → dropdown → Save. Now the ♂/♀ next to the name is a two-button segmented control that sets it immediately on click (gender-only PATCH; exclude_unset on the backend leaves the name/other fields alone). The active sex is highlighted; click it again to clear. Full edit form still has the gender field.
Setting sex required Edit → dropdown → Save. Now the ♂/♀ next to the name is a two-button segmented control that sets it immediately on click (gender-only PATCH; `exclude_unset` on the backend leaves the name/other fields alone). The active sex is highlighted; click it again to clear. Full edit form still has the gender field.
tsc clean; build passes.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Setting a person's sex meant clicking Edit, opening a dropdown, and saving.
Replace the read-only ♂/♀ symbol next to the name with an always-visible
two-button segmented control that PATCHes immediately on click (gender-only;
backend PATCH is exclude_unset so the name/other fields are untouched).
Clicking the active sex clears it. The full edit form still offers gender for
completeness.
Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Signed-off-by: Justin Paul <[email protected]>
justin
merged commit b51b65de80 into main2026-06-08 22:03:32 -04:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Setting sex required Edit → dropdown → Save. Now the ♂/♀ next to the name is a two-button segmented control that sets it immediately on click (gender-only PATCH;
exclude_unseton the backend leaves the name/other fields alone). The active sex is highlighted; click it again to clear. Full edit form still has the gender field.tsc clean; build passes.
🤖 Generated with Claude Code