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 #6308] [CLOSED] ci: cherry-pick to main by default #6581

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

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/6308
Author: @himself65
Created: 11/25/2025
Status: ❌ Closed

Base: canary ← Head: himself65/2025/11/25/pick

📝 Commits (6)

  • ec70a85 ci: cherry-pick to main by default
  • 1ec245b ci: cherry-pick to main by default
  • 45ac2d8 ci: cherry-pick to main by default
  • 6fcad33 ci: cherry-pick to main by default
  • f0753da ci: cherry-pick to main by default
  • db69759 ci: cherry-pick to main by default

📊 Changes

1 file changed (+25 additions, -1 deletions)

View changed files

📝 .github/workflows/cherry-pick-to-main.yml (+25 -1)

📄 Description

Summary by cubic

Auto-labels new PRs targeting canary with “merge-to-main” so cherry-pick to main runs by default and no manual labeling is needed. Uses a pull_request_target trigger on canary to apply the label when a PR is opened or reopened, and prevents the cherry-pick job from running on pull_request events.

Written for commit db69759d84. 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/6308 **Author:** [@himself65](https://github.com/himself65) **Created:** 11/25/2025 **Status:** ❌ Closed **Base:** `canary` ← **Head:** `himself65/2025/11/25/pick` --- ### 📝 Commits (6) - [`ec70a85`](https://github.com/better-auth/better-auth/commit/ec70a8571af37b531f4ba43cb359455b36c529fa) ci: cherry-pick to main by default - [`1ec245b`](https://github.com/better-auth/better-auth/commit/1ec245be009db60c91fd4f6ce5a5fcb5e22f43ba) ci: cherry-pick to main by default - [`45ac2d8`](https://github.com/better-auth/better-auth/commit/45ac2d8bf2aabd1655b1abcbf56bcea960cf40bb) ci: cherry-pick to main by default - [`6fcad33`](https://github.com/better-auth/better-auth/commit/6fcad33623bc56ac1e415145552910f1a8288784) ci: cherry-pick to main by default - [`f0753da`](https://github.com/better-auth/better-auth/commit/f0753da948094d4a57f1c69abb663b4cd61b68bb) ci: cherry-pick to main by default - [`db69759`](https://github.com/better-auth/better-auth/commit/db69759d84c5bccbc2589fc0f4a753461ef40eb0) ci: cherry-pick to main by default ### 📊 Changes **1 file changed** (+25 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `.github/workflows/cherry-pick-to-main.yml` (+25 -1) </details> ### 📄 Description <!-- This is an auto-generated description by cubic. --> ## Summary by cubic Auto-labels new PRs targeting canary with “merge-to-main” so cherry-pick to main runs by default and no manual labeling is needed. Uses a pull_request_target trigger on canary to apply the label when a PR is opened or reopened, and prevents the cherry-pick job from running on pull_request events. <sup>Written for commit db69759d84c5bccbc2589fc0f4a753461ef40eb0. 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 13:04:04 -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#6581
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?