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

[PR #6976] [MERGED] ci: remove auto cherry pick #15248

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

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/6976
Author: @himself65
Created: 12/24/2025
Status: ✅ Merged
Merged: 12/24/2025
Merged by: @himself65

Base: canary ← Head: himself65/2025/12/24/auto-cherry-pick

📝 Commits (1)

  • 01ea2c9 ci: remove auto cherry pick

📊 Changes

2 files changed (+0 additions, -662 deletions)

View changed files

➖ .github/workflows/auto-cherry-pick-to-main.yml (+0 -337)
➖ .github/workflows/cherry-pick-to-main.yml (+0 -325)

📄 Description

Auto-cherry-pick CI breaks for the 1.4.8 release, as we ignore some missing commits. So I will remove these two CI as these won't help us but even worse

Summary by cubic

Removed the two GitHub Actions that auto cherry-picked from canary to main (auto-cherry-pick-to-main.yml and cherry-pick-to-main.yml) because they failed during the 1.4.8 release by ignoring missing commits and causing risky merges. This simplifies CI and prevents incorrect cherry-picks to main.

Written for commit 01ea2c9be0. 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/6976 **Author:** [@himself65](https://github.com/himself65) **Created:** 12/24/2025 **Status:** ✅ Merged **Merged:** 12/24/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `himself65/2025/12/24/auto-cherry-pick` --- ### 📝 Commits (1) - [`01ea2c9`](https://github.com/better-auth/better-auth/commit/01ea2c9be01e65f7c1da04aca7040895660e3a71) ci: remove auto cherry pick ### 📊 Changes **2 files changed** (+0 additions, -662 deletions) <details> <summary>View changed files</summary> ➖ `.github/workflows/auto-cherry-pick-to-main.yml` (+0 -337) ➖ `.github/workflows/cherry-pick-to-main.yml` (+0 -325) </details> ### 📄 Description Auto-cherry-pick CI breaks for the 1.4.8 release, as we ignore some missing commits. So I will remove these two CI as these won't help us but even worse <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Removed the two GitHub Actions that auto cherry-picked from canary to main (auto-cherry-pick-to-main.yml and cherry-pick-to-main.yml) because they failed during the 1.4.8 release by ignoring missing commits and causing risky merges. This simplifies CI and prevents incorrect cherry-picks to main. <sup>Written for commit 01ea2c9be01e65f7c1da04aca7040895660e3a71. 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-13 09:54: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#15248
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?