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 #6115] [MERGED] chore: update google credentials instructions #6456

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

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/6115
Author: @Paola3stefania
Created: 11/20/2025
Status: ✅ Merged
Merged: 11/20/2025
Merged by: @himself65

Base: canary ← Head: chore/improve-google-doc

📝 Commits (1)

  • 6cc389a chore: update google credentials instructions

📊 Changes

1 file changed (+16 additions, -0 deletions)

View changed files

📝 docs/content/docs/authentication/google.mdx (+16 -0)

📄 Description

This PR improves the Google SSO documentation by adding a small callout showing the exact steps to create OAuth credentials inside the Google Cloud Console.

Many developers (especially beginners) struggle to locate the correct menu path in Google Cloud, leading to:
• redirect_uri_mismatch errors
• Confusion between API Keys, OAuth Client IDs, and Web Applications
• Misconfigured redirect URLs and missing credentials

What’s Added

A concise, 5-step guide under the Google provider section explaining:
1. Where to click in Google Cloud Console
2. How to create an OAuth Client ID
3. Web Application settings
4. Redirect URIs for local + production
5. Where to place the Client ID / Secret

This addition removes ~80% of reported onboarding friction while keeping the existing documentation structure intact.

image

Summary by cubic

Improved Google SSO docs with a short callout that walks through creating OAuth credentials in Google Cloud. It covers creating an OAuth Client ID, setting redirect URIs for local and production, and adding the Client ID/Secret to env to avoid redirect_uri_mismatch.

Written for commit 6cc389aeb3. Summary will update automatically on new commits.

🔄 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/6115 **Author:** [@Paola3stefania](https://github.com/Paola3stefania) **Created:** 11/20/2025 **Status:** ✅ Merged **Merged:** 11/20/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `chore/improve-google-doc` --- ### 📝 Commits (1) - [`6cc389a`](https://github.com/better-auth/better-auth/commit/6cc389aeb3f87d5d406abd6abfe9ced8a39cd728) chore: update google credentials instructions ### 📊 Changes **1 file changed** (+16 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/authentication/google.mdx` (+16 -0) </details> ### 📄 Description This PR improves the Google SSO documentation by adding a small callout showing the exact steps to create OAuth credentials inside the Google Cloud Console. Many developers (especially beginners) struggle to locate the correct menu path in Google Cloud, leading to: • redirect_uri_mismatch errors • Confusion between API Keys, OAuth Client IDs, and Web Applications • Misconfigured redirect URLs and missing credentials What’s Added A concise, 5-step guide under the Google provider section explaining: 1. Where to click in Google Cloud Console 2. How to create an OAuth Client ID 3. Web Application settings 4. Redirect URIs for local + production 5. Where to place the Client ID / Secret This addition removes ~80% of reported onboarding friction while keeping the existing documentation structure intact. <img width="854" height="650" alt="image" src="https://github.com/user-attachments/assets/55edbc0d-1292-4368-a21c-bace2ff4f058" /> <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Improved Google SSO docs with a short callout that walks through creating OAuth credentials in Google Cloud. It covers creating an OAuth Client ID, setting redirect URIs for local and production, and adding the Client ID/Secret to env to avoid redirect_uri_mismatch. <sup>Written for commit 6cc389aeb3f87d5d406abd6abfe9ced8a39cd728. Summary will update automatically on new commits.</sup> <!-- End of auto-generated description by cubic. --> --- <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 12:59:56 -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#6456
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?