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

[PR #6117] [MERGED] chore: update drizzle docs #32059

New Issue
Closed
opened 2026-04-17 22:55:29 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-17 22:55:29 -05:00
Owner
Copy Link

📋 Pull Request Information

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

Base: canary ← Head: chore/improve-drizzle-docs

📝 Commits (2)

  • 4f4de0c chore: update drizzle docs
  • 02cfca7 Merge branch 'canary' into chore/improve-drizzle-docs

📊 Changes

1 file changed (+44 additions, -7 deletions)

View changed files

📝 docs/content/docs/adapters/drizzle.mdx (+44 -7)

📄 Description

This PR enhances the Drizzle ORM adapter documentation with the missing steps developers need to successfully use Better Auth with Drizzle.

Why

Many developers generate the Better Auth schema but aren’t sure what to do next.
This leads to frequent issues such as missing tables, schema mismatches, and migration errors.

What’s Added

•	Clarified where the generated Better Auth schema should be placed
•	Added instructions to merge Better Auth schema with the app’s Drizzle schema
•	Added step to pass the merged schema into drizzleAdapter
•	Added a clear workflow for:
•	Generating migrations
•	Applying migrations
•	Verifying tables with Drizzle Studio

This creates a complete and reliable setup flow for developers integrating Better Auth with Drizzle ORM.

image

Summary by cubic

Updated Drizzle ORM adapter docs with a clear, end-to-end setup for Better Auth: where to place the generated auth schema, how to merge it with your app schema, how to pass the merged schema to drizzleAdapter, and how to run and verify migrations. Added guidance for custom table name mappings (e.g., mapping Better Auth’s user to your users table).

Written for commit 4f4de0cd52. 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/6117 **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-drizzle-docs` --- ### 📝 Commits (2) - [`4f4de0c`](https://github.com/better-auth/better-auth/commit/4f4de0cd52099059783c554f8a2c546f803281d2) chore: update drizzle docs - [`02cfca7`](https://github.com/better-auth/better-auth/commit/02cfca7eec0145d6e11410ba879ae7504c46717b) Merge branch 'canary' into chore/improve-drizzle-docs ### 📊 Changes **1 file changed** (+44 additions, -7 deletions) <details> <summary>View changed files</summary> 📝 `docs/content/docs/adapters/drizzle.mdx` (+44 -7) </details> ### 📄 Description This PR enhances the Drizzle ORM adapter documentation with the missing steps developers need to successfully use Better Auth with Drizzle. Why Many developers generate the Better Auth schema but aren’t sure what to do next. This leads to frequent issues such as missing tables, schema mismatches, and migration errors. **What’s Added** • Clarified where the generated Better Auth schema should be placed • Added instructions to merge Better Auth schema with the app’s Drizzle schema • Added step to pass the merged schema into drizzleAdapter • Added a clear workflow for: • Generating migrations • Applying migrations • Verifying tables with Drizzle Studio This creates a complete and reliable setup flow for developers integrating Better Auth with Drizzle ORM. <img width="865" height="824" alt="image" src="https://github.com/user-attachments/assets/a900c3f3-0ab5-47b6-88a4-d9d77b384c7d" /> <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Updated Drizzle ORM adapter docs with a clear, end-to-end setup for Better Auth: where to place the generated auth schema, how to merge it with your app schema, how to pass the merged schema to drizzleAdapter, and how to run and verify migrations. Added guidance for custom table name mappings (e.g., mapping Better Auth’s user to your users table). <sup>Written for commit 4f4de0cd52099059783c554f8a2c546f803281d2. 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-04-17 22:55:29 -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#32059
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?