docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 3a513123#982
docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 3a513123#982docschina-bot wants to merge 7 commits into
Conversation
Co-authored-by: Hiroshi Ogawa <hi.ogawa.zz@gmail.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: 0468f40fc9
ℹ️ 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".
| // write X in a test?" If yes, it belongs here. Mocking sub-pages | ||
| // live nested because they're a multi-page subtopic. | ||
| { | ||
| <<<<<<< HEAD |
There was a problem hiding this comment.
When the docs site reads .vitepress/config.ts, this raw <<<<<<< HEAD marker is invalid TypeScript, so VitePress cannot parse the config and the docs build/startup will fail before rendering any page. I also checked the changed files with rg "^(<<<<<<<|=======|>>>>>>>)" and found the same unresolved conflict markers in multiple newly merged Markdown files, so this merge needs conflict resolution before it can be shipped.
Useful? React with 👍 / 👎.
5 participants
此 PR 自动生成。
合并 vitest-dev/docs-cn 的修改至本仓库（@ 3a51312）
以下文件存在冲突，可能需要重新翻译：
请解决所有冲突后提交到此 pull request，可直接在 Github 修改、切换到 sync-3a513123-1 分支进行修改或者使用 Github Desktop 拉取此 pr 修改并提交。
禁止使用 Squash Merge 来合并此 Pull Request！
使用该操作会导致上游仓库的内容丢失，并致使下一次合并产生冲突。