safe-deploy

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

NEVER deploy to production without first verifying the branch includes all commits from
origin/main
.

This prevents the critical bug where a feature branch deploys older code that overwrites recently merged PRs.

在未先验证分支包含
origin/main
的所有提交之前，绝对不要部署到生产环境。

这可以防止功能分支部署旧代码覆盖最近合并的PR这一严重问题。

Run these checks in order:

Fetch latest main
bash
```
git fetch origin main
```
Check if branch is up-to-date
bash
```
git merge-base --is-ancestor origin/main HEAD
```
- Exit code 0 = safe to deploy
- Exit code 1 = STOP, branch is behind main
If behind, show missing commits
bash
```
git log --oneline origin/main ^HEAD
```
Merge before deploying
bash
```
git merge origin/main
```
Run tests after merge
bash
```
npx vitest run
```
Only then deploy

按顺序执行以下检查：

拉取最新的main分支
bash
```
git fetch origin main
```
检查分支是否为最新版本
bash
```
git merge-base --is-ancestor origin/main HEAD
```
- 退出码0 = 可以安全部署
- 退出码1 = 停止，分支落后于main分支
若分支落后，显示缺失的提交
bash
```
git log --oneline origin/main ^HEAD
```
部署前合并分支
bash
```
git merge origin/main
```
合并后运行测试
bash
```
npx vitest run
```
仅在完成上述步骤后部署

Projects should have a

predeploy

npm script that runs

scripts/pre-deploy-check.mjs

automatically before

npm run deploy

. If the project has this script, always use

npm run deploy

instead of calling the deploy tool directly.

项目应配置

predeploy

npm脚本，在

npm run deploy

自动运行

scripts/pre-deploy-check.mjs

。如果项目有此脚本，请始终使用

npm run deploy

，而非直接调用部署工具。