Repository navigation
chore: publish Astro landing to GitHub Pages via Actions - #120
Merged
Merged
Conversation
Re-enable project Pages with a workflow-only deploy of landing/ (no Jekyll root build). Astro site/base and PUBLIC_APP_URL keep assets and CTAs correct on github.io while Vercel root deploys stay unchanged.
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.
Summary
.github/workflows/pages.yml: checkout → Node 22 →npm install→build:landingwith Pages env →upload-pages-artifact→deploy-pages.base/PUBLIC_SITE_URLfor project Pages (/taskflow-calendar/); asset paths and font URLs base-aware.PUBLIC_APP_URLon Pages builds so Sign in / Start free hit the Vercel app; unset on Vercel so relative/app/*stays.build_type: workflow(no Jekyll on monorepo root).Test plan
PUBLIC_*Pages landing build succeeds; asset paths under/taskflow-calendar/./favicon.svgand/app/*.