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

[PR #5125] [MERGED] ci: remove main branch protection rules #5793

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

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/5125
Author: @himself65
Created: 10/6/2025
Status: ✅ Merged
Merged: 10/6/2025
Merged by: @himself65

Base: canary ← Head: himself65/2025/10/06/ci

📝 Commits (1)

  • df5f9b0 ci: remove main branch protection rules

📊 Changes

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

View changed files

➖ .github/workflows/branch-rules.yml (+0 -36)
➖ .github/workflows/main-protect.yml (+0 -18)

📄 Description

We use GitHub rules from settings, so we don't need this CI in code

Summary by cubic

Removed GitHub Actions that enforced main branch protection. PRs with code changes are no longer forced to target canary or v*-staging, and main PRs are no longer restricted by source branch.

🔄 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/5125 **Author:** [@himself65](https://github.com/himself65) **Created:** 10/6/2025 **Status:** ✅ Merged **Merged:** 10/6/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `himself65/2025/10/06/ci` --- ### 📝 Commits (1) - [`df5f9b0`](https://github.com/better-auth/better-auth/commit/df5f9b0325767dec52bee4e33376d15815a7db1f) ci: remove main branch protection rules ### 📊 Changes **2 files changed** (+0 additions, -54 deletions) <details> <summary>View changed files</summary> ➖ `.github/workflows/branch-rules.yml` (+0 -36) ➖ `.github/workflows/main-protect.yml` (+0 -18) </details> ### 📄 Description We use GitHub rules from settings, so we don't need this CI in code <!-- This is an auto-generated description by cubic. --> ## Summary by cubic Removed GitHub Actions that enforced main branch protection. PRs with code changes are no longer forced to target canary or v*-staging, and main PRs are no longer restricted by source branch. <!-- 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:36:17 -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#5793
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?