docs(en): merge docs-cn/sync-docs into docs-cn/dev @ e7f79533#992
Conversation
Co-authored-by: Codex <noreply@openai.com> Co-authored-by: Hiroshi Ogawa <4232207+hi-ogawa@users.noreply.github.com>
Co-authored-by: Hiroshi Ogawa <4232207+hi-ogawa@users.noreply.github.com> Co-authored-by: Codex <noreply@openai.com>
✅ Deploy Preview for cn-vitest ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: dcc6047650
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| - 向 CLI 传递 `--config` 选项，例如 `vitest --config ./path/to/vitest.config.ts`。 | ||
| - 使用 `process.env.VITEST` 或在 `defineConfig` 上的 `mode` 属性（如果没有用 `--mode` 覆盖，默认设置为 `test`）也可以在 `vite.config.ts` 中有条件地应用不同的配置。请注意，像任何其他环境变量一样，`VITEST` 也会在测试中的 `import.meta.env` 上暴露出来。 | ||
|
|
||
| <<<<<<< HEAD |
There was a problem hiding this comment.
This commit leaves unresolved merge-conflict markers in the rendered Markdown, so the docs will either publish <<<<<<</=======/>>>>>>> verbatim or fail downstream content checks. I found the same pattern with rg '^(<<<<<<<|=======|>>>>>>>)' in api/advanced/vitest.md, guide/browser/why.md, guide/learn/writing-tests.md, and guide/migration.md as well, so this merge needs to be resolved before shipping.
Useful? React with 👍 / 👎.
6 participants
此 PR 自动生成。
合并 vitest-dev/docs-cn 的修改至本仓库（@ e7f7953）
以下文件存在冲突，可能需要重新翻译：
请解决所有冲突后提交到此 pull request，可直接在 Github 修改、切换到 sync-e7f79533-1 分支进行修改或者使用 Github Desktop 拉取此 pr 修改并提交。
禁止使用 Squash Merge 来合并此 Pull Request！
使用该操作会导致上游仓库的内容丢失，并致使下一次合并产生冲突。