Repository navigation
Publish independently built CFS at /2027/cfs/ - #2
Merged
Merged
Conversation
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
1 participant
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 2027 Pages deployment currently publishes only the main website. Include the independently built sponsorship site at
/2027/cfs/by checking outsitcon-tw/2027-cfs'sbuildbranch and copying its generated files intodist/cfs/before publication.CFS dependencies and Google Sheet fetching remain entirely in the CFS repository. This workflow only reads its output, records the consumed commit, and fails before publication if
index.htmlis missing. No cross-repository writes, deploy keys, schedules, or data commits are introduced.Validation: both sites pass Astro checks and local builds; the CFS importer reads the new 2027 Sheet (40 items, four plans). Browser smoke tests passed for the main page, Chinese and English CFS pages, direct item pages, and quotations, with no JavaScript errors or missing local resources. The first successful CFS build is required before merging.