From 2ad4f6a43b1e0005eb4c5eb1c753ed4d1cbf7a89 Mon Sep 17 00:00:00 2001
From: boratatouille <178141691+boratatouille@users.noreply.github.com>
Date: Thu, 22 Oct 2026 21:09:07 +0800
Subject: [PATCH] Point contributors at main instead of development

---
 CONTRIBUTING.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 4bf849d..a5112cf 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -1,13 +1,12 @@
 # Contributing to Basecoat
 
 - Support development by sponsoring the author: https://github.com/sponsors/hunvreus
-- Submit pull requests (PRs) against the `development` branch, not `main`.
+- Submit pull requests (PRs) against the `main` branch.
 - For branches, we have:
   - `main` is our production and default branch. This is what we deploy to https://basecoatui.com and publish to https://www.npmjs.com/package/basecoat-css.
-  - `development` is for staging. We will deploy it soon at https://dev.basecoatui.com.
   - New features are worked in `feature/name-of-the-feature` branches.
-  - Issues are addressed in `issue/123-main-isse` branches.
-  - When ready, we PR against `development`, test it and then finally merge to `main`.
+  - Issues are addressed in `issue/123-main-issue` branches.
+  - When ready, open a PR against `main`.
 - Keep changes focused: one feature or fix per PR.
 - Test locally before submitting.
 - Follow existing code style.