Skip to content

docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 7df7a657#973

Closed
docschina-bot wants to merge 3 commits into
devfrom
sync-7df7a657-1
Closed

docs(en): merge docs-cn/sync-docs into docs-cn/dev @ 7df7a657#973
docschina-bot wants to merge 3 commits into
devfrom
sync-7df7a657-1

Conversation

@docschina-bot
Copy link
Copy Markdown
Collaborator

此 PR 自动生成。

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

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

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

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

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

@docschina-bot docschina-bot requested a review from elonehoo May 12, 2026 23:53
@netlify
Copy link
Copy Markdown

netlify Bot commented May 12, 2026

Deploy Preview for cn-vitest failed.

Name Link
🔨 Latest commit 65ba420
🔍 Latest deploy log https://app.netlify.com/projects/cn-vitest/deploys/6a03bd617722fc0008039a61

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: 65ba420cd3

ℹ️ 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/browser/commands.md
Comment on lines +129 to +132
<<<<<<< HEAD
### 自定义 `playwright` 命令 {#custom-playwright-commands}
=======
### Recording trace markers
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 leftover merge conflict markers

This file still contains Git conflict markers (<<<<<<<, =======, >>>>>>>), which means the merge was committed unresolved; Markdown tooling and site generation can surface these markers verbatim (or fail validation), and readers will see two competing section versions instead of one canonical document. Please resolve the conflict and keep only the intended content.

Useful? React with 👍 / 👎.

@NoiseFan NoiseFan closed this May 14, 2026
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.

4 participants