Skip to content

The complete open source platform to run your entire marketplace. Storefront, vendor panel, admin console, and integrations in one enterprise-grade platform you own.

docs: fix broken links and references to deleted new branch (#1636)

Mohammad Mahdi Arshadi(Metolini)47bacd00aafc
diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 0ec75fd4a..dcd513f3e 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -24,7 +24,7 @@ Describe what actually happened, including screenshots or logs if helpful.
## Environment
-- Branch: `new` / other?
+- Branch: `main` / other?
- Module or area:
- Browser/Runtime:
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 23947f286..f2c0abe05 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -12,7 +12,7 @@ List the tests or commands you ran to validate the change.
## Checklist
-- [ ] This pull request targets `new`.
+- [ ] This pull request targets `main`.
- [ ] I updated documentation, locales if the change requires it.
- [ ] I added or adjusted tests that cover the change.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index dd6d0cfae..9f4bb8ab1 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -4,19 +4,18 @@ We’re excited to collaborate with folks building on top of Mercur. This guide
## Branch Model
-- `main` – release-ready code. Every commit is tagged and deployable. Keep PRs targeting `main` limited to hotfixes or release prep approved by maintainers.
-- `new` – nightly builds and upcoming release work. Base regular feature work off `new` so it can soak in automation and shared testing.
+- `main` – main branch containing release-ready code. Base regular feature work off `main`.
- Topic branches – create a dedicated branch per change using the format `feat/<concise-feature-name>` (for example `feat/vendor-product-export`). Use other prefixes when appropriate (`fix/`, `chore/`, `docs/`).
## Working on Features
-- Branch from `new`, keeping it up to date via `git pull --rebase origin new`.
+- Branch from `main`, keeping it up to date via `git pull --rebase origin main`.
- Keep commits scoped and descriptive. Squash locally if it clarifies the story.
- Follow module conventions from [`CLAUDE.md`](CLAUDE.md) and prefer the `packages/` workspace for new code.
## Pull Requests
-- Open PRs against `new` unless you are coordinating a release hotfix.
+- Open PRs against `main`.
- Describe the user impact, architectural notes, and testing performed (lint, unit, integration, CLI).
- Ensure the branch merges cleanly and CI is green before requesting review.
- Reference related issues or discussions; add screenshots or recordings for UI tweaks.
diff --git a/README.md b/README.md
index b799114b4..b40bb7361 100644
--- a/README.md
+++ b/README.md
@@ -131,7 +131,7 @@ Mercur is built and maintained by [Rigby](https://rigbyjs.com), a team that has
## Contribution
-Mercur is an Open Source project and we encourage everyone to help us make it better. If you are interested in contributing to the project, please read our [Contributing Guide](https://raw.githubusercontent.com/mercurjs/mercur/refs/heads/new/CONTRIBUTING.md) and [Code of Conduct](https://raw.githubusercontent.com/mercurjs/mercur/refs/heads/new/CODE_OF_CONDUCT.md).
+Mercur is an Open Source project and we encourage everyone to help us make it better. If you are interested in contributing to the project, please read our [Contributing Guide](./CONTRIBUTING.md) and [Code of Conduct](./CODE_OF_CONDUCT.md).
If you have any questions about contributing, please join our [Discord server](https://discord.gg/hnZBzc4NJU) - we are happy to help you!
diff --git a/packages/cli/README.md b/packages/cli/README.md
index d550e8279..b701cb7f3 100644
--- a/packages/cli/README.md
+++ b/packages/cli/README.md
@@ -342,7 +342,7 @@ The CLI uses a `blocks.json` file for configuration. This file is created when y
```json
{
- "$schema": "https://raw.githubusercontent.com/mercurjs/mercur/new/packages/registry/schema/registry.json",
+ "$schema": "https://registry.mercurjs.com/registry.json",
"aliases": {
"workflows": "packages/api/src/workflows",
"api": "packages/api/src/api",