chore: add vault versions v1.4.x through v1.6.x to develop #549
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
Contributor
Vercel Previews Deployed
|
Contributor
Broken Link CheckerReport exceeds max length of 65536 characters, so it cannot be displayed in GitHub comments. Download full report. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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
This PR migrates the rest of the vault docs to the develop branch of UDR. Most of this is just from the migration script but there are a few other changes I had to make:
@inlcude partials/file_name.mdx. I updated them to just be@include file_name.mdxlike the other versions so our api could find the filespartials/telemetry-metrics/vault/cachepartial files. Our .gitignore file was ignoring files that had the foldercache. I removed that line from the gitignore and also added the files back in.Testing
Since all vault files are included in this branch, some testing would be good. I've done a bit but it would be good if someone else could double check too.
npm run prebuildnpm run devvaultto theunified_docs_migrated_reposflag in theconfig/unified-docs-sandbox.jsonfile.UNIFIED_DOCS_APIto behttp://localhost:8080in the .env fileHASHI_ENV=unified-docs-sandbox npm starthttp://localhost:3000and checkout a few of the vault docs from different versions to verify you aren't seeing any issues with images, partials, and just general docs