docs: List release versions for each function, add unreleased label #1868
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
hairyhenderson
force-pushed
the
docs-filter-by-release
branch
from
2268efe to
fd05eb3
Compare
hairyhenderson
changed the title
hairyhenderson
force-pushed
the
docs-filter-by-release
branch
from
fd05eb3 to
09fea1d
Compare
Signed-off-by: Dave Henderson <[email protected]>
hairyhenderson
force-pushed
the
docs-filter-by-release
branch
from
09fea1d to
e59395c
Compare
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.
Fixes #1839
Instead of generating two separate doc sites, this adds a label to each function to indicate the version of gomplate it was released in. That way I can still document unreleased functions, but it'll be more clear that they're not available in released builds yet.
(I didn't want to generate multiple doc sites because the docs overhaul I did in #1729 is only in
main, and so I'd have had to backport that to the 3.11.x branch, which is likely more trouble than it's worth)