Repository navigation
fix(ci): deploy production site with GitHub Pages Actions - #529
Closed
vitormattos wants to merge 1 commit into
Closed
vitormattos wants to merge 1 commit into
vitormattos wants to merge 1 commit into
Conversation
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
Contributor
|
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
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
The production
Deployworkflow reports success after pushing the generated site togh-pages, but the separate legacy GitHub Pages deployment fails. On November 3 the build updated the branch successfully while Pages remained inupdating_pagesuntil a 10-minute timeout; the public site still served the October 25 build.Changes
actions/deploy-pages, making the deploy result part of the same workflow.pages: writeandid-token: writepermissions required for the deployment.Validation and rollout
gh-pagesbranch; the new deployment job will not take over until Pages is switched to Actions. The domainlibresign.coopmust remain configured.Deployworkflow (manual dispatch is already enabled), confirmDeploy to GitHub Pagessucceeds, then checkhttps://libresign.coop/_deployment-info.jsonfor the new SHA. Do not treat the build alone as proof of publication.Separate finding
The
LibreSign/site-previewdeployment branch contains approximately 1.93 GB across 23 PR preview folders; 21 belong to closed PRs. That is a separate GitHub Pages limit failure and requires cleanup of stale preview content. The current preview workflow points togh-pages; historical failed PR builds used an older revision targeting protectedmain.No production merge is performed by this PR.