fix(cd): trigger GitHub Pages deployment via API after git push #152
Conversation
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
- Push to gh-pages branch (reliable, no hanging) - Trigger deployment via GitHub Pages API (fast, uses GitHub CDN) - Best of both worlds: reliable upload + fast deployment
Contributor
Author
|
不再需要 - 已配置从 gh-pages 分支部署，git push 会自动触发部署。 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Problem
上一个 PR (#151) 使用 git push 到 gh-pages 分支解决了
upload-pages-artifact卡住的问题，但需要手动配置 GitHub Pages 从分支部署，且无法利用 GitHub Actions 部署的速度优势。Solution
混合方案：
这样既避免了
upload-pages-artifact的问题，又能保持 GitHub Actions 部署的速度。Changes
Push to gh-pages branch: git push 到 gh-pagesTrigger GitHub Pages deployment: 调用 GitHub Pages API 触发部署