From 041c03bf11bf983279a9da7dbce8c851bb1b0509 Mon Sep 17 00:00:00 2001 From: pewdiepie-archdaemon Date: Thu, 4 Jun 2026 20:52:18 +0900 Subject: [PATCH] Add dev/main branch model: PRs target dev, main is curated Switching to a two-branch workflow: contributors open PRs against `dev`, and `main` is fast-forwarded to a tested `dev` commit at each release. This separates "things land in staging" (can move fast) from "things ship to users" (slow, tested in a browser by the maintainer first). CONTRIBUTING: add a Branch model section explaining the split + how to retarget a PR. PR template: add an explicit "this PR targets dev" checkbox at the top so it's the first thing a contributor confirms. End-users cloning the repo will now land on `dev` by default; they can `git checkout main` if they want the curated branch. --- .github/pull_request_template.md | 4 ++++ CONTRIBUTING.md | 11 +++++++++++ 2 files changed, 15 insertions(+) diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md index 8afee6d..e9ed637 100644 --- a/.github/pull_request_template.md +++ b/.github/pull_request_template.md @@ -2,6 +2,10 @@ +## Target branch + +- [ ] This PR targets **`dev`**, not `main`. All PRs land in `dev`; `main` is curated by the maintainer at each release. If your PR is on `main` by accident, click "Edit" on this PR and change the base. + ## Linked Issue