Skip to content

fix(sponsor-panel): fake email shim for private GitHub users - #1197

Merged
Xe merged 2 commits into
mainfrom
Xe/fake-email-shim
Apr 2, 2026
Merged

fix(sponsor-panel): fake email shim for private GitHub users#1197
Xe merged 2 commits into
mainfrom
Xe/fake-email-shim

Conversation

@Xe

@Xe Xe commented Apr 2, 2026

Copy link
Copy Markdown
Owner

Summary

  • Generate login@fake-address.invalid for GitHub users who don't expose a public email, instead of rejecting them with "Email address required"
  • Shim applied at both OAuth callback (new users) and Thoth token handler (existing users with empty emails in DB)
  • Fix renderError to return HTTP 200 so HTMX actually swaps error messages into card target elements (HTMX drops non-2xx responses by default)

Test plan

  • Log in with a GitHub account that has no public email, verify fake email is generated and stored
  • Request a Thoth token with that account, verify it succeeds
  • Trigger an error condition (e.g. non-sponsor), verify the error message appears in the card

Xe added 2 commits April 2, 2026 12:17
… HTMX error display

Users with private GitHub emails were rejected when requesting a Thoth
token. Now generates login@fake-address.invalid instead. Also changed
renderError to return HTTP 200 so HTMX actually swaps error messages
into the target elements (HTMX drops non-2xx responses by default).

Assisted-by: Claude Opus 4.6 via Claude Code
Signed-off-by: Xe Iaso <me@xeiaso.net>
Assisted-by: Claude Opus 4.6 via Claude Code
Signed-off-by: Xe Iaso <me@xeiaso.net>
@github-actions

github-actions Bot commented Apr 2, 2026

Copy link
Copy Markdown

The latest Buf updates on your PR. Results from workflow Buf / protobuf (pull_request).

BuildFormatLintBreakingUpdated (UTC)
✅ passed✅ passed✅ passed⏩ skippedApr 2, 2026, 11:19 AM

@Xe
Xe merged commit ff89f87 into main Apr 2, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant