feat: build the Amplify previews with Astro - #504
Merged
Merged
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
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.
Step B of the Astro migration: switch the pull request previews to Astro.
amplify.ymlbuildsastro/on Node 26 withSITE_PREVIEW=true(entries dated in the future are shown in previews). Without this file Amplify keeps using the Jekyll build spec of the console.CONTRIBUTING.mdexplains how to contribute with Astro.Production is untouched: GitHub Pages still deploys the Jekyll build until the next PR.
Rollback: revert this PR, Amplify goes back to the console build spec.
Review on this preview: one Article, one Talk, one
redirect_from,/blog/page2/, fonts and navbar icons, dark mode, search, a page that uses{:toc}, a Mermaid page, a future-dated entry.