This repository was archived by the owner on Dec 18, 2024. It is now read-only.
build: ensure docs-content is up-to-date before deploy #505
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
* Currently the `fetch-assets` script always fetches the data from the `master` branch. This is problematic because if we release a new patch release, we will incorrectly have the docs content for the upcoming major version. * Adds a small note that makes the publisher aware of the docs-content that should be kept updated.
|
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
fetch-assetsscript always fetches the data from themasterbranch. This is problematic because if we release a new patch release, we will incorrectly have the docs content for the upcoming major version. Adds the possibility to fetch the docs-content from a given branch (e.g.6.4.x)deployscript that makes the publisher aware of the docs-content, which should be kept updated.This is related to angular/components#12690 (comment)