From 19909746f55fba1bf8d15832c6d4f713c1f05dfc Mon Sep 17 00:00:00 2001 From: zhangwenjian Date: Fri, 28 Aug 2026 20:36:24 +0800 Subject: [PATCH] =?UTF-8?q?docs=F0=9F=93=9D:=20drop=20VitePress=20containe?= =?UTF-8?q?r=20syntax=20GitHub=20cannot=20render?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `:::tip` and its closing `:::` are VitePress custom containers. GitHub has no such syntax, so both markers rendered as literal text: a paragraph beginning ":::tip" and a stray ":::" sitting alone above the next heading. The Chinese README carries the same warning as a plain paragraph, which GitHub renders correctly, so the English one now matches it. Verified through GitHub's own markdown API: the literal marker no longer appears in the output and the warning survives as ordinary text. Only README.md was affected; the other three never had it. --- README.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/README.md b/README.md index b466fe94..c043e677 100644 --- a/README.md +++ b/README.md @@ -155,7 +155,7 @@ vi ./config/settings.yml # 2. Confirm the log path ``` -:::tip ⚠️Note that this problem will occur if CGO is not installed in the windows10+ environment; +⚠️ Note that this problem will occur if CGO is not installed in the windows10+ environment; ```bash E:\go-admin>go build @@ -173,8 +173,6 @@ cgo: exec gcc: exec: "gcc": executable file not found in %PATH% [Solve the cgo problem and enter](https://www.go-admin.pro/guide/faq#cgo-%E7%9A%84%E9%97%AE%E9%A2%98) -::: - #### Initialize the database, and start the service ``` bash