docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 829251fd#969
docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 829251fd#969
Conversation
…ake 2) (#10031) Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com> Co-authored-by: Codex <noreply@openai.com> Co-authored-by: Ari Perkkiö <ari.perkkio@gmail.com>
…itest/blob/` (#10232)
✅ Deploy Preview for cn-vitest ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 8f022965e3
ℹ️ 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".
| function mergeReports(directory?: string): Promise<TestRunResult> | ||
| ``` | ||
|
|
||
| <<<<<<< HEAD |
There was a problem hiding this comment.
Resolve leftover merge-conflict markers in docs
This merge commit leaves raw conflict markers (<<<<<<<, =======, >>>>>>>) in published Markdown, which causes the docs to render broken conflict text and duplicate contradictory content instead of a single resolved explanation. The same unresolved pattern appears in multiple files changed by this commit (api/advanced/vitest.md, guide/cli.md, guide/improving-performance.md, and guide/reporters.md), so users reading these pages will see merge artifacts rather than valid documentation.
Useful? React with 👍 / 👎.
此 PR 自动生成。
合并 vitest-dev/docs-cn 的修改至本仓库(@ 829251f)
以下文件存在冲突,可能需要重新翻译:
请解决所有冲突后提交到此 pull request,可直接在 Github 修改、切换到 sync-829251fd-1 分支进行修改或者使用 Github Desktop 拉取此 pr 修改并提交。
禁止使用 Squash Merge 来合并此 Pull Request!
使用该操作会导致上游仓库的内容丢失,并致使下一次合并产生冲突。