Add instructions for creating a new API version #30
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
lbernick
force-pushed
the
conversion-docs
branch
from
7f45275 to
44eeee4
Compare
This commit splits developer documentation into separate files, with a table of contents to help developers find docs more easily. It also reorganizes the results documentation to more clearly separate results documentation from results implementation (except in the case of a known issue with our implementation).
lbernick
force-pushed
the
conversion-docs
branch
from
44eeee4 to
ecb56ea
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.
This commit adds instructions for creating a new version of Pipelines CRDs.
It is based off of the doc "How to add a new API version for your CRD"
(https://docs.google.com/document/d/1omfO0O4yoUuM1Fk2E6wjfdVNK6XFSmxI3pb13xQ3rys).
Putting it into the developer documentation will make these instructions more discoverable
and allow others to edit them.
Changes
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes