Repository navigation
docs: 更正 Pages 迁移的操作顺序 - #23
Merged
Merged
Conversation
原文写的「先合并、再切 build_type、然后触发部署」是错的，照做会踩一次 竞态：push 到 master 会同时触发 legacy 构建（从 master:/docs 出，因为那时 build_type 还是 legacy）与工作流的部署，谁后落地谁赢。实测 legacy 那次晚 3 秒完成，把 Actions 的部署盖掉了 —— 症状是 deploy job 报绿但站点内容没变。 真实顺序是：切完 build_type 之后再手动跑一次 gh workflow run pages.yml。
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
补 #22 合并后才暴露出来的一段。
CLAUDE.md 里原本写的迁移顺序是「先合并、再切
build_type、然后立刻触发部署」，实际照做会踩一次竞态：push 到 master 会同时触发两条路 ——build_type还是legacy时 GitHub 用自己的构建器从master:/docs出一版，工作流也提交一版部署，谁后落地谁赢。实测结果：
症状很有迷惑性：deploy job 报绿、
pages/builds/latest也是一条成功的构建，但站点内容仍是旧的。当时排查了 9 分钟才排除掉 CDN 缓存这个可能。正确顺序是切完
build_type之后再手动跑一次gh workflow run pages.yml（此后不会再有新的 legacy 构建，跑一次就站住）。文档里补了症状与排查入口（gh api repos/{owner}/{repo}/pages/builds/latest看 commit 是不是刚推的那个）。纯文档修正，不动代码。