feat: check command docs are up to date #1219
Merged
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
gotbadger
force-pushed
the
ci/docgen-check
branch
from
2f47a51
to
f4c96ab
Compare
gotbadger
force-pushed
the
ci/docgen-check
branch
5 times, most recently
from
9e93c51
to
de59aa8
Compare
gotbadger
force-pushed
the
ci/docgen-check
branch
2 times, most recently
from
b1e9508
to
3d4fdf9
Compare
gotbadger
force-pushed
the
ci/docgen-check
branch
from
3d4fdf9
to
dfe39f8
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.
Description
In #414 we identifed that sometimes we forget to generate command data files for the docs. Considering we dont want to add go as a build dependancy this seems like the best option to make sure the command data files stay up to date.
Related
closes #414
Checklist