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 #1439] [MERGED] fix:(docs) google logo colors compliance in builder #3807

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

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/1439
Author: @Maqed
Created: 2/14/2025
Status: ✅ Merged
Merged: 2/14/2025
Merged by: @Bekacru

Base: main ← Head: fix(docs)-brand-logo-compliance

📝 Commits (1)

  • cb01ff8 fix: google logo colors compliance

📊 Changes

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

View changed files

📝 docs/components/builder/social-provider.tsx (+10 -21)

📄 Description

Basically google doesn't always allow the modification of their logo by changing its color as stated in their Brand Resource Center.
image
So, I changed it to fit all use-cases.

🔄 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/1439 **Author:** [@Maqed](https://github.com/Maqed) **Created:** 2/14/2025 **Status:** ✅ Merged **Merged:** 2/14/2025 **Merged by:** [@Bekacru](https://github.com/Bekacru) **Base:** `main` ← **Head:** `fix(docs)-brand-logo-compliance` --- ### 📝 Commits (1) - [`cb01ff8`](https://github.com/better-auth/better-auth/commit/cb01ff8c904723f03e0a0d3c054ea9fba99a95f1) fix: google logo colors compliance ### 📊 Changes **1 file changed** (+10 additions, -21 deletions) <details> <summary>View changed files</summary> 📝 `docs/components/builder/social-provider.tsx` (+10 -21) </details> ### 📄 Description Basically google doesn't always allow the modification of their logo by changing its color as stated in their [Brand Resource Center.](https://about.google/brand-resource-center/brand-elements/) ![image](https://github.com/user-attachments/assets/a4c5cfe4-99be-47b8-b988-9482d9f99310) So, I changed it to fit all use-cases. --- <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:14:07 -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#3807
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?