devadmin/ProLibertateGames
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Activity

Merge pull request #41 from adrianoftyriel/cf-treat-1014-as-absent

Browse Source 
Treat Cloudflare 1014 as 'channel not published yet'
This commit is contained in:
adrianoftyriel
2026-10-14 10:02:26 -06:00
committed by GitHub
parent 0b74b1b2b1 2df140a3c1
commit 12d20565bd
1 changed files with 6 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
.github/scripts/stage-pages-site.sh
+6
View File
@@ -38,6 +38,12 @@ fi
# failure must stop the deploy rather than silently dropping that channel. # failure must stop the deploy rather than silently dropping that channel.
code="$(curl -sS -o "$out/$other/latest.json" -w '%{http_code}' "$base/$other/latest.json" || true)" code="$(curl -sS -o "$out/$other/latest.json" -w '%{http_code}' "$base/$other/latest.json" || true)"
: "${code:=000}" : "${code:=000}"
# Cloudflare error 1014 (403 + "error code: 1014") means the domain's CNAME
# points at a Pages project that does not exist yet, so there is nothing to
# preserve — the same as a 404, and what a push-triggered first deploy sees.
if [ "$code" = 403 ] && grep -q 'error code: 1014' "$out/$other/latest.json" 2>/dev/null; then
code=404
fi
if [ "$code" = 404 ]; then if [ "$code" = 404 ]; then
echo "No $other channel published yet; skipping." echo "No $other channel published yet; skipping."
rm -rf "$out/$other" rm -rf "$out/$other"