chore(tests): tie usage output to snapshots #3246
Closed
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
wraithgar
force-pushed
the
gar/test-usage-snapshot
branch
2 times, most recently
from
5c20371 to
15721c9
Compare
darcyclarke
added
Release 7.x
isaacs
pushed a commit
that referenced
this pull request
May 20, 2021
We have another PR in flight that will start auto-generating some content in `docs/content/commands`, and will run `postsnap`, which means that if we tie the usage output to a snapshot, the docs will also be updated when the snapshots change. PR-URL: #3246 Credit: @wraithgar Close: #3246 Reviewed-by: @isaacs
isaacs
force-pushed
the
gar/test-usage-snapshot
branch
from
15721c9 to
55f2c2a
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.
We have another PR in flight that will start auto-generating some
content in
docs/content/commands, and will runpostsnap, which meansthat if we tie the usage output to a snapshot, the docs will also be
updated when the snapshots change.
References
Related to #3243