{{ message }}
feat: allow using custom markers on pkg level#95
Merged
Conversation
This was referenced Oct 4, 2024
thbkrkr
reviewed
Oct 17, 2024
czeslavo
force-pushed
the
feat/propagate-pkg-markers
branch
from
7b078b7 to
80ec94a
Compare
admacleod
pushed a commit
to kubeshop/crd-ref-docs
that referenced
this pull request
Sep 4, 2025
This starts propagating package-level markers so they can be used in templates if desired (similar to field and type-level markers).
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
3 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.
This starts propagating package-level markers so they can be used in templates if desired (similar to field and type-level markers).