Update Nightly GitHub action to pull docs from astro repo#13176
Merged
Conversation
sarah11918
added
the
ci
✅ Deploy Preview for astro-docs-2 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Co-authored-by: Armand Philippot <[email protected]>
sarah11918
added
the
merge-on-release
ArmandPhilippot
approved these changes
Jan 30, 2026
ArmandPhilippot
left a comment
ArmandPhilippot
left a comment
Member
There was a problem hiding this comment.
Looks better now, and I think this is all we need! 🙌🏽
Co-authored-by: Chris Swithinbank <[email protected]>
delucis
approved these changes
Jan 30, 2026
matthewp
added a commit
that referenced
this pull request
Jun 15, 2026
Armand pointed out this should follow the same release-branch transition pattern used for v6 in #13176 and #13373, rather than removing main updates entirely or renaming the generated v7 PR branches. During this phase, the docs repository still has two relevant branches: - docs main is still the current v6 documentation branch. - docs v7 is the upcoming v7 documentation branch. The Astro framework repository has v7 on main now, and also has a 6-legacy branch for any last-minute v6 fixes. That means the nightly generated reference jobs should keep two matrix entries: - SOURCE_BRANCH: 6-legacy, TARGET_BRANCH: main, so current docs do not receive v7-generated reference content but can still pick up v6 fixes. - SOURCE_BRANCH: main, TARGET_BRANCH: v7, so the v7 docs branch receives generated reference updates from the framework main branch. This mirrors #13176, where the previous docs main branch sourced from 5-legacy while the v6 docs branch sourced from framework main. The later post-merge cleanup is the separate #13373-style step: switch docs main back to source main and comment out the version-branch entry after v7 itself is merged.
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
3 participants
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.
Description (required)
The
withastro/astrorepo will soon usemainfor v6 beta code, and a5-legacybranch for v5 code. This updates the nightly GitHub action to pull in config reference and errors to represent these new source branches for code to make sure docs get to the right branch!Don't merge until @florian-lefebvre makes the corresponding change in the astro repo!