Fix versioning filename examples - #131
Open
lntutor wants to merge 1 commit into
Open
Conversation
Author
|
Current head b40a71c is mergeable, and I do not see any unresolved review threads or contributor-side follow-up remaining on the current PR state. This looks ready for maintainer review when someone has a chance. |
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
1 participant
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.
Fixes #117.
Updates every
VersioningXX.jsonreference in the versioning guide to the documentedVersioning_XX.jsonfilename template.Validation:
mkdocs buildVersioningXX.jsonreferences remain in the guidegit diff --checkmkdocs build --strictstill reports the repository existing unresolved-link warnings; the regular CI-equivalent build completes successfully.