github-starred/better-auth
2
0
Fork 0
mirror of https://github.com/better-auth/better-auth.git synced 2026-05-23 07:18:56 -05:00
Code Issues 2.5k Packages Projects Releases 112 Wiki Activity

[PR #3285] [CLOSED] feat:Add Discord OAuth email scope configuration field #4736

New Issue
Closed
opened 2026-03-13 11:58:05 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-03-13 11:58:05 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/3285
Author: @Summerlytz
Created: 7/7/2025
Status: ❌ Closed

Base: main ← Head: main

📝 Commits (1)

  • fd25440 Add Discord OAuth email scope configuration field

📊 Changes

1 file changed (+21 additions, -3 deletions)

View changed files

📝 packages/better-auth/src/social-providers/discord.ts (+21 -3)

📄 Description

Collecting the real email address is a privacy concern. By implementing this simple fix, it allows users to replace said address with a dummy address easily. I understand you can write over the email field, but this removes the SCOPE which is important as the user understands their email is being sent.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/better-auth/better-auth/pull/3285 **Author:** [@Summerlytz](https://github.com/Summerlytz) **Created:** 7/7/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`fd25440`](https://github.com/better-auth/better-auth/commit/fd254402543e0ffdaf7ccd8d161bed89d41961cc) Add Discord OAuth email scope configuration field ### 📊 Changes **1 file changed** (+21 additions, -3 deletions) <details> <summary>View changed files</summary> 📝 `packages/better-auth/src/social-providers/discord.ts` (+21 -3) </details> ### 📄 Description Collecting the real email address is a privacy concern. By implementing this simple fix, it allows users to replace said address with a dummy address easily. **I understand you can write over the email field, but this removes the SCOPE which is important as the user understands their email is being sent.** --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-03-13 11:58:05 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
adapter
astro
awaiting external contributor
blocked
breaking
breaking change
bug
c-devops
core
credentials
database
dependencies
devops
devtools
docs
documentation
duplicate
elysia
enhancement
enterprise
expo
express
fastify
good first issue
help wanted
hono
identity
infra
integration
invalid
javascript
locked
maintenance
need-more-information
needs: info
needs: repro
nextjs
nuxt
oauth
organization
P0
payments
perf
platform
plugin
pull-request
Mirrored from GitHub Pull Request
 question
ready
regression
remix
security
social-provider
solid
stale
svelte
tanstack-start
tracking
version-bump
vue
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/better-auth#4736
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?