| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
is the only allowed comment
|
|
configure-pages@v5 with enablement: true fails on a fresh repo with
"Resource not accessible by integration" — creating a Pages site is
administration-scoped and the workflow's GITHUB_TOKEN only carries
pages: write, which is enough to deploy but not to provision.
The one-time manual step is: Settings → Pages → Source: GitHub Actions.
After that, this workflow is idempotent and deploys on every push.
|
|
configure-pages fails on first run when Pages hasn't been turned on in
the repo yet. Passing enablement: true lets the workflow provision the
Pages site using its own pages:write token — no manual Settings → Pages
trip needed, and subsequent runs are idempotent.
|
|
On push to main: install with frozen lockfile, type-check with
svelte-check, lint, then build with BASE_PATH set to /<repo-name>
so kit.paths.base produces correct asset URLs under the GH Pages
subdomain. Artifact uploaded via actions/upload-pages-artifact@v3
and deployed via actions/deploy-pages@v4.
Concurrency group 'pages' prevents overlapping deploys from
stepping on each other; cancel-in-progress left off so a queued
deploy from a later commit waits for the earlier one to finish
rather than aborting it mid-upload.
|
