Fix: Deprecate old target_path specification in repo-config.yml#24
Draft
Fix: Deprecate old target_path specification in repo-config.yml#24
Conversation
❌ Deploy Preview for gardenlinux-docs failed.
|
Collaborator
Author
|
given that the current build error is caused by failing to resolve a path, I would say the goal of the PR is achieved. |
41731cf to
48e6c8f
Compare
48e6c8f to
db4cefe
Compare
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
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.
What this PR does / why we need it:
This PR should fix the current build issue relating to target path mapping for supporting tools. It deprecates the old methods of specifying the output path for aggregated docs, which is now handled by the docs frontmatter. Specifically the
github_target_pathentry of the frontmatter.Which issue(s) this PR fixes:
Fixes #23
Definition of Done:
main)