Repository navigation
docs: show quoted heredocs for multi-line triage Reports - #1730
Merged
Merged
Conversation
This was referenced Nov 4, 2026
Merged
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
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.
Summary
Document how to paste multi-line Reports into a Triage run and regenerate the published manual.
Closes #1728
Evidence
printfpipe and--file, without a quoted heredoc for pasted Reports.After: the Markdown and generated manual show a multi-line quoted heredoc and explain why its contents stay literal. Executing the documented example in Bash with a stdin-capture stub preserved the Report byte for byte; decoding the HTML code block preserved the copyable command.
npm run docs:check --prefix sitepassed.scripts/affected-tests mainpassed:npm test --prefix site(61 tests),cargo test --test share_card --test site_deploy, andcargo test --bin thirdshift prompts_page.Merge Danger
Door: two-way
Blast Radius: documentation
Unaddressed findings
Standards
None. The review raised 0 findings.
Spec
None. The review raised 0 findings.
Security
None. The review raised 0 findings.
Security review outcome
No unaddressed introduced findings.
Review coverage
Both reviewers read the changed hunks in
docs/guide.mdandsite/docs/index.html. No changed file was left unread; there were no generated-output exclusions.Built with codex codex-cli 0.164.0 · gpt-6.1-sol · xhigh