Check if CLI docs have been committed during CI #3132
Merged
Conversation
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
AS CLI reference docs is generated during build, we should ensure that they have been committed and pushed whenever a they are changed. Signed-off-by: Kim Christensen <[email protected]>
kichristensen
force-pushed
the
checkCliDocsCommitted
branch
2 times, most recently
from
a45cba1 to
18c2a0e
Compare
kichristensen
requested review from
bdegeeter,
schristoff,
sgettys and
troy0820
as code owners
schristoff
approved these changes
May 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
What does this change
As CLI reference docs is generated during build, we should ensure that they have been committed and pushed whenever a they are changed.
What issue does it fix
Closes #551
Notes for the reviewer
Checklist