Repository navigation
ci: deploy the site with actions/deploy-pages - #501
Merged
Merged
Conversation
mnencia
force-pushed
the
dev/pages-from-actions
branch
from
October 21, 2026 10:09
1b6a85d to
2641b16
Compare
gbartolini
approved these changes
Oct 21, 2026
The site was published by pushing the built files to the gh-pages branch, so anyone with write access could push a commit there and change the live site without a build or review. Upload the built site as a Pages artifact and deploy it with actions/deploy-pages instead. Only a run on the production branch deploys, and the build job is read-only. This needs the Pages source set to GitHub Actions. The README publishing section is updated to match. Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
mnencia
force-pushed
the
dev/pages-from-actions
branch
from
October 21, 2026 10:24
2641b16 to
0fc64f5
Compare
mnencia
changed the title
gbartolini
pushed a commit
to cloudnative-pg/cnpg-infra
that referenced
this pull request
Oct 21, 2026
) Before this change, `scripts/check-repo-settings.sh cloudnative-pg.github.io` reported `Build type: workflow (expected: legacy)`. With it, build type, source (`production/`) and custom domain all match, with no drift. The site change is cloudnative-pg/cloudnative-pg.github.io#501. Signed-off-by: Marco Nenciarini <marco.nenciarini@enterprisedb.com>
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.
The site was published by pushing the built files to the gh-pages branch, so anyone with write access could push a commit there and change the live site without a build or review. Upload the built site as a Pages artifact and deploy it with actions/deploy-pages instead. Only a run on the production branch deploys, and the build job is read-only. This needs the Pages source set to GitHub Actions. The README publishing section is updated to match.
Do not fast-forward production after merging this until the Pages source is switched, or the deploy job fails and the site stays on its last version.
Switching the source is a repository setting, not part of this PR. Order that keeps the downtime short:
gh api -X PUT repos/cloudnative-pg/cloudnative-pg.github.io/pages -f build_type=workflow -f cname=cloudnative-pg.io -F https_enforced=true, then immediately re-run the failed deploy job, which reuses the build artifact.build_type=legacy.Checked so far: actionlint passes, and a manual run from this branch only builds. The built public/ has the same 4,203 files as the gh-pages branch except CNAME and .nojekyll, which only matter for branch-based Pages. The docs site at /docs/ is a separate project site and takes its domain from this repository's Pages settings, which stay. The action versions are the same pinned v5 releases that cloudnative-pg/docs uses.