vados-cosmonic opened PR #10666 from vados-cosmonic:refactor(docs)=update-code-blocks to bytecodealliance:main:
This commit udpates more instructions on various READMEs to avoid
$for easy copy-pasting, and also useconsolewhere appropriate.<!--
Please make sure you include the following information:
If this work has been discussed elsewhere, please include a link to that
conversation. If it was discussed in an issue, just mention "issue #...".Explain why this change is needed. If the details are in an issue already,
this can be brief.Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.htmlPlease ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->
vados-cosmonic requested fitzgen for a review on PR #10666.
vados-cosmonic requested wasmtime-fuzz-reviewers for a review on PR #10666.
vados-cosmonic requested wasmtime-compiler-reviewers for a review on PR #10666.
vados-cosmonic requested wasmtime-default-reviewers for a review on PR #10666.
vados-cosmonic requested wasmtime-core-reviewers for a review on PR #10666.
github-actions[bot] commented on PR #10666:
Subscribe to Label Action
cc @cfallin, @fitzgen
<details>
This issue or pull request has been labeled: "cranelift", "fuzzing", "isle", "wasmtime:docs"Thus the following users have been cc'd because of the following labels:
- cfallin: isle
- fitzgen: fuzzing, isle
To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.
Learn more.
</details>
dicej submitted PR review:
There are several blocks you've marked
consolewhich include$prompts and/or command output (I've added inline comments for a few, but then got tired of repeating myself). I'm thinking those should all be markedshell-sessiongiven they can't be meaningfully cut-and-pasted, correct?
dicej created PR review comment:
This looks like it should remain a
shell-sessionblock given the$prompt and command output.
dicej created PR review comment:
Given the
(lldb)prompt, it seems like this should be neitherconsolenorshbut maybe justtext?
dicej created PR review comment:
Should this be
shell-session?
dicej created PR review comment:
Should this be
shell-session?
dicej created PR review comment:
Should this be
shell-session?
vados-cosmonic submitted PR review.
vados-cosmonic created PR review comment:
Yeah I think that's right, will update!
vados-cosmonic submitted PR review.
vados-cosmonic created PR review comment:
Yup, will fix!
vados-cosmonic updated PR #10666.
vados-cosmonic submitted PR review.
vados-cosmonic created PR review comment:
Updated!
vados-cosmonic submitted PR review.
vados-cosmonic created PR review comment:
Updated!
vados-cosmonic submitted PR review.
vados-cosmonic created PR review comment:
Updated!
vados-cosmonic requested dicej for a review on PR #10666.
dicej submitted PR review.
dicej created PR review comment:
This should probably just be
text-- the reader doesn't need to cut-and-paste command output.
dicej created PR review comment:
This one's tricky because they'll need to edit the content after cut-and-pasting it before running. Maybe we should use the same strategy here as we do on line 43, e.g.
cargo +nightly fuzz run $MY_FUZZ_TARGET $MY_TEST_CASE
vados-cosmonic submitted PR review.
vados-cosmonic created PR review comment:
Yeah, so I thought about making this text, but technically they should see it in the console... Will change this to text!
vados-cosmonic submitted PR review.
vados-cosmonic created PR review comment:
Ah good point -- Yes, I think using some well named fill-in ENV vars is better here
vados-cosmonic requested dicej for a review on PR #10666.
vados-cosmonic commented on PR #10666:
Thanks for the reviews @dicej ! Addressed the feed back :bow:
vados-cosmonic edited a comment on PR #10666:
Thanks for the reviews @dicej ! Addressed the feedback :bow:
dicej submitted PR review.
alexcrichton closed without merge PR #10666.
alexcrichton commented on PR #10666:
Er ok sorry so this was stuck in "Checking mergabilty..." so I thought I could kick github into action by closing/reopening it. Now it's not letting me reopen this, though... @vados-cosmonic mind re-sending this? (or maybe you can reopen it?)
alexcrichton commented on PR #10666:
Well now it's letting me reopen ... ?
alexcrichton commented on PR #10666:
Well, I swear it gave me a button "Reopen and comment", I hit it, and then it stayed closed... I don't think github likes me right now. I no longer have the possibility of hitting the button...
vados-cosmonic commented on PR #10666:
Hery @alexcrichton no worries! I'll re-open this. Weirdly enough it's not showing the re-open button for me either? I guess no one gets to re-create this PR :sweat_smile:
Last updated: Dec 06 2025 at 06:05 UTC