fix(schema): move config-schema into docs folder #3878
Merged
Conversation
This file contains 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
matchai
approved these changes
Apr 16, 2022
matchai
changed the title
davidkna
added a commit
to davidkna/starship
that referenced
this pull request
Apr 18, 2022
This reverts PR starship#3878 / commit 094f982.
5 tasks
davidkna
added a commit
to davidkna/starship
that referenced
this pull request
Apr 18, 2022
This reverts PR starship#3878 / commit 094f982.
davidkna
added a commit
that referenced
this pull request
Apr 18, 2022
This was referenced Jun 26, 2022
This was referenced Aug 14, 2022
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.
Description
This PR moves the config schema file from
.github/intodocs/.vuepress/public/instead of using a symlink. The existing symlink path may have been invalid (it is printed in red the GitHub UI).I also considered moving config schema generation into the deploy step, but that could make it harder to build the docs if it ends up using the file for documentation generation.
Motivation and Context
Closes #
Screenshots (if appropriate):
How Has This Been Tested?
Checklist: