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

[PR #4455] [MERGED] chore: encode merge rules to a github workflow #30995

New Issue
Closed
opened 2026-04-17 21:57:30 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-17 21:57:30 -05:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/better-auth/better-auth/pull/4455
Author: @frectonz
Created: 9/5/2025
Status: ✅ Merged
Merged: 9/5/2025
Merged by: @himself65

Base: canary ← Head: chore/branch-rules

📝 Commits (4)

  • 74df719 chore: encode merge rules to a github workflow
  • b5f99b6 fix: compare against head
  • 314855d chore: fix formatting
  • 1ee824e fix: use paths filter

📊 Changes

2 files changed (+42 additions, -18 deletions)

View changed files

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

📄 Description

This PR encodes the merge rules we have been using into a github action. The rules are the following

  • All docs change PRs must be targeting main
  • All other PRs must target canary

Summary by cubic

Adds a GitHub Action to enforce PR branch targets. Docs-only PRs must target main; all other changes must target canary or a versioned -staging branch.

  • New Features

    • New Branch Rules workflow runs on PRs to main, canary, and v*-staging.
    • Checks changed files; if only docs/*, base must be main; otherwise base must be canary or vX.Y.Z-staging.

  • Refactors

    • Removed the old main-protect workflow in favor of this unified rule set.

🔄 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/4455 **Author:** [@frectonz](https://github.com/frectonz) **Created:** 9/5/2025 **Status:** ✅ Merged **Merged:** 9/5/2025 **Merged by:** [@himself65](https://github.com/himself65) **Base:** `canary` ← **Head:** `chore/branch-rules` --- ### 📝 Commits (4) - [`74df719`](https://github.com/better-auth/better-auth/commit/74df7194c25388af1f59cde9741cd7007bdae49c) chore: encode merge rules to a github workflow - [`b5f99b6`](https://github.com/better-auth/better-auth/commit/b5f99b671cbe85c1d1fbcf77fe4416b5f0c1f343) fix: compare against head - [`314855d`](https://github.com/better-auth/better-auth/commit/314855dbfbe7e9ca52ffa935f8d2f8841ae6b4d8) chore: fix formatting - [`1ee824e`](https://github.com/better-auth/better-auth/commit/1ee824eeb0e5b8be884d23550060277b571cf14d) fix: use paths filter ### 📊 Changes **2 files changed** (+42 additions, -18 deletions) <details> <summary>View changed files</summary> ➕ `.github/workflows/branch-rules.yml` (+42 -0) ➖ `.github/workflows/main-protect.yml` (+0 -18) </details> ### 📄 Description This PR encodes the merge rules we have been using into a github action. The rules are the following - All `docs` change PRs must be targeting `main` - All other PRs must target `canary` <!-- This is an auto-generated description by cubic. --> --- ## Summary by cubic Adds a GitHub Action to enforce PR branch targets. Docs-only PRs must target main; all other changes must target canary or a versioned -staging branch. - **New Features** - New Branch Rules workflow runs on PRs to main, canary, and v*-staging. - Checks changed files; if only docs/*, base must be main; otherwise base must be canary or vX.Y.Z-staging. - **Refactors** - Removed the old main-protect workflow in favor of this unified rule set. <!-- 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 21:57:30 -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#30995
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?