This is an automated email from the ASF dual-hosted git repository.

lizhimins pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/rocketmq-dashboard.git


The following commit(s) were added to refs/heads/master by this push:
     new d50ffecc9 docs: update development trunk branch to rocketmq-studio
d50ffecc9 is described below

commit d50ffecc9d7e8f8f46da64198831bd7952e6974e
Author: lizhimins <[email protected]>
AuthorDate: Thu Sep 17 21:11:39 2026 +0800

    docs: update development trunk branch to rocketmq-studio
---
 CONTRIBUTING.md | 18 +++++++++---------
 README.md       |  2 +-
 README_zh.md    |  2 +-
 3 files changed, 11 insertions(+), 11 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index f4e7cf54a..efaeb4772 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -5,13 +5,13 @@ development environment, how changes are reviewed and merged, 
and what we expect
 pull request.
 
 RocketMQ Studio is developed in this repository (`apache/rocketmq-dashboard`) 
on the
-**`master`** branch, which is also the repository default branch. All pull 
requests must
-target `master`.
+**`rocketmq-studio`** branch, which is also the repository default branch. All 
pull requests must
+target `rocketmq-studio`.
 
 | Branch | Role |
 |--------|------|
-| `master` | RocketMQ Studio trunk — base your branches and pull requests on 
it |
-| `master_archive` | Archive of the legacy rocketmq-dashboard code that lived 
on `master` before. Read-only history, not for development |
+| `rocketmq-studio` | RocketMQ Studio trunk — base your branches and pull 
requests on it |
+| `master_archive` | Archive of the legacy rocketmq-dashboard code that lived 
on the trunk before. Read-only history, not for development |
 
 Recommended background reading:
 
@@ -87,18 +87,18 @@ English strings to `web/src/i18n/` whenever you add UI text.
    projects decide by consensus: a new feature, a new API or a large refactor 
should be
    agreed on in the issue before the implementation lands. This saves you from 
having a
    finished pull request rejected on design grounds.
-4. **Fork, branch, commit.** Create your branch from `master`:
+4. **Fork, branch, commit.** Create your branch from `rocketmq-studio`:
 
    ```bash
    git clone [email protected]:<your-username>/rocketmq-dashboard.git
    git remote add upstream https://github.com/apache/rocketmq-dashboard.git
-   git fetch upstream master
-   git checkout -b <your-topic> upstream/master
+   git fetch upstream rocketmq-studio
+   git checkout -b <your-topic> upstream/rocketmq-studio
    ```
 
-5. **Open a pull request against `master`** and link the issue with `Fixes 
#<issue-id>` so
+5. **Open a pull request against `rocketmq-studio`** and link the issue with 
`Fixes #<issue-id>` so
    it closes automatically on merge.
-6. **Keep it current.** Rebase onto `upstream/master` when the branch moves; 
force-push
+6. **Keep it current.** Rebase onto `upstream/rocketmq-studio` when the branch 
moves; force-push
    your own fork branch as needed.
 
 Pull requests are merged with **squash merge only**, so the merged commit 
message becomes
diff --git a/README.md b/README.md
index f59d38f08..40b6fe272 100644
--- a/README.md
+++ b/README.md
@@ -80,7 +80,7 @@ development.
 
 ## Development Guidelines
 
-- **Branches** — `master` is the development trunk: base your branches and 
pull requests on it. `master_archive` keeps the legacy dashboard history and is 
not used for development. See [CONTRIBUTING.md](CONTRIBUTING.md) for the full 
workflow
+- **Branches** — `rocketmq-studio` is the development trunk: base your 
branches and pull requests on it. `master_archive` keeps the legacy dashboard 
history and is not used for development. See [CONTRIBUTING.md](CONTRIBUTING.md) 
for the full workflow
 - **Code Style** — ESLint + Prettier for frontend, Husky pre-commit hook for 
auto-check
 - **Commit Format** — Conventional Commits (`feat:` / `fix:` / `refactor:` / 
`chore:` / `docs:` / `perf:`)
 - **Architecture Tests** — `mvn test` runs ArchUnit hexagonal architecture 
constraint checks
diff --git a/README_zh.md b/README_zh.md
index 3b6a35ec8..4a3f68f74 100644
--- a/README_zh.md
+++ b/README_zh.md
@@ -70,7 +70,7 @@ cd .. && docker compose up -d --build
 
 ## 开发规范
 
-- **分支说明** — `master` 是开发主干,请基于它切分支、提 PR;`master_archive` 是原 dashboard 
的历史归档,不用于开发;完整流程见 [CONTRIBUTING.md](CONTRIBUTING.md)
+- **分支说明** — `rocketmq-studio` 是开发主干,请基于它切分支、提 PR;`master_archive` 是原 
dashboard 的历史归档,不用于开发;完整流程见 [CONTRIBUTING.md](CONTRIBUTING.md)
 - **代码风格** — 前端通过 ESLint + Prettier 统一格式,Husky pre-commit hook 自动检查
 - **Commit 格式** — 遵循 Conventional Commits(`feat:` / `fix:` / `refactor:` / 
`chore:` / `docs:` / `perf:`)
 - **架构测试** — 后端 `mvn test` 自动运行 ArchUnit 六边形架构约束检查

Reply via email to