Update the documentation smoke test to use the smoke test token #3608
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
finestructure
approved these changes
Jan 16, 2025
daveverwer
force-pushed
the
docs-smoke-test-token
branch
from
df4934d to
c4658fa
Compare
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.
I updated and used the
Run create-restfile docscommand to generate this version of the Rester file with theX-SPI-Smoke-Testheader in, but it seems like the docs test has drifted a little from when it was originally generated.I have commented out the three packages that were previously commented out, but it's still quite a big diff and we may want not to make the other changes that running the command produces as part of this PR. That said, I think we should give this one a go so it's more in sync with what the tool produces.