Skip to content

docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 1f86109e#964

Closed
docschina-bot wants to merge 7 commits intodevfrom
sync-1f86109e-1
Closed

docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 1f86109e#964
docschina-bot wants to merge 7 commits intodevfrom
sync-1f86109e-1

Conversation

@docschina-bot
Copy link
Copy Markdown
Collaborator

此 PR 自动生成。

合并 vitest-dev/docs-cn 的修改至本仓库(@ 1f86109

以下文件存在冲突,可能需要重新翻译:

请解决所有冲突后提交到此 pull request,可直接在 Github 修改、切换到 sync-1f86109e-1 分支进行修改或者使用 Github Desktop 拉取此 pr 修改并提交。

禁止使用 Squash Merge 来合并此 Pull Request!

使用该操作会导致上游仓库的内容丢失,并致使下一次合并产生冲突。

@docschina-bot docschina-bot requested a review from elonehoo April 22, 2026 23:40
@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 22, 2026

Deploy Preview for cn-vitest failed.

Name Link
🔨 Latest commit a785e16
🔍 Latest deploy log https://app.netlify.com/projects/cn-vitest/deploys/69e95c5ea37f210008d659ed

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a785e16773

ℹ️ 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".

Comment thread api/assert.md

## isOk

<<<<<<< HEAD
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Resolve merge conflict markers before publishing docs

This commit leaves raw Git conflict markers in rendered documentation (for example <<<<<<< HEAD at this location), which means users will see unresolved merge artifacts and conflicting content variants instead of a single authoritative doc. The same pattern appears across many files in this change set, so the docs output is materially corrupted until these conflicts are resolved.

Useful? React with 👍 / 👎.

@NoiseFan NoiseFan closed this Apr 24, 2026
@NoiseFan NoiseFan deleted the sync-1f86109e-1 branch April 24, 2026 15:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants