镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

docs: turn the README into a landing page, and run help examples with --execute - #20

Merged
thebrandonlucas merged 1 commit into
masterfrom
docs/help-examples-execute
Oct 20, 2026
Merged

thebrandonlucas merged 1 commit into
masterfrom
docs/help-examples-execute

Conversation

@thebrandonlucas

@thebrandonlucas thebrandonlucas commented Oct 9, 2026 •

Copy link
Copy Markdown
Contributor

Stack: master ← #20 ← #22 ← #57 ← #24 ← #19 ← #26 ← #27 ← #28 ← #29 ← #30 ← #55. Rebased onto master (#53, #56) on 2026-10-19.

Summary

This PR has two parts. #21 (README landing page) was merged into this branch, so the title now covers both.

  • Help examples: the payments receive and wallets create help examples now pass --execute. Before, copying them only described the request and exited 6.
  • Example test: a unit test parses every voltage example through the real command tree: each shell block in the Markdown user docs and the development guide, and every Examples: line in each command's long help. A non-GET example must pass --execute or --dry-run. Placeholder IDs (WALLET_ID, ORG_ID, …) stand in for UUIDs. Arguments split on whitespace, so a quoted argument that contains spaces is not supported.
  • Docs reorganization: the 240-line README is now a 92-line landing page: logo, pitch, install, quick start, scripting example, and a docs table. The rest moves, mostly verbatim, into docs/guides, docs/reference, and docs/concepts, with an index at docs/README.md. The note on docs/plans moves to AGENTS.md.
  • Link test: each relative link and image path must reach a file, and each anchor a heading.

Changes after review

  • Rebased onto master. AGENTS.md keeps both "Before you request review" (docs(agents): require skill review and the CRAP report before review #56) and "Work plans".
  • The README exit-code row for 4 again covers transport failures: "Transport failure, or a payment whose outcome is unknown".
  • The install guide says that rust-toolchain.toml applies to builds from a clone, not to cargo install --git.
  • The example test reads only .md files under docs/, so an image or other asset cannot break it.

Checks

On 761d86a:

  • cargo fmt --check, cargo clippy --locked --all-targets -- -D warnings, cargo machete --with-metadata: pass.
  • cargo test --locked: 90 unit and 61 integration tests pass. VOLTAGE_BLESS=1 cargo test --locked leaves the tree clean.
  • python3 scripts/check-coverage.py: pass.
  • CRAP (scripts/crap-report.sh): no function at or above 20. Highest is api::wait_for_payment at 19.66, unchanged from or lower than master (19.66).
  • Skill review: voltage-pr-review and the voltage-backend-engineering Rust checklist, against the stack base. Findings are fixed in this commit.

Not run: the staging and live tutorials, which need credentials.

tee8z
tee8z previously approved these changes Oct 9, 2026

@tee8z tee8z left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, just some minor suggestions/questions

Comment thread docs/concepts/safety-model.md Resolved
Comment thread docs/guides/payments.md Resolved
… --execute

The payments receive and wallets create help examples left out --execute,
so copying them only described the request and exited 6. Both now pass
--execute.

A unit test now parses every voltage line in the user docs' shell blocks
and every Examples line in each command's long help through the real
command tree. Placeholder IDs stand in for UUIDs. An example that is not a
GET must pass --execute or --dry-run, so a documented change cannot
silently stop at a description again. It covers every Markdown user doc
and the development guide, in sh, bash, shell, and console fences at any
indent. Arguments are split on whitespace, so a quoted argument with
spaces is not supported.

The README was a 240-line manual. It is now a 92-line landing page: the
Voltage logo (light and dark variants from the brand guide), a one-line
pitch, three reasons to use it, install, a quick start that ends in a
payment, a scripting example with the key exit codes, and a table of docs.
Everything else moves, mostly verbatim, into docs/ by kind: guides
(install, login and profiles, payments, requests, checkout, scripting),
reference (output, exit codes), and concepts (the safety model), with an
index at docs/README.md. The note on docs/plans moves to AGENTS.md.

A new test checks that each relative link and HTML image path reaches an
existing file, and each anchor an existing heading outside code fences.
The development guide's staging receive example now passes --execute.
@thebrandonlucas
thebrandonlucas force-pushed the docs/help-examples-execute branch from 38915c6 to 761d86a Compare October 20, 2026 11:58
@thebrandonlucas
thebrandonlucas removed this pull request from stack #25 October 20, 2026 11:59
@thebrandonlucas
thebrandonlucas added this pull request to stack #58 October 20, 2026 11:59
@thebrandonlucas thebrandonlucas changed the title fix(cli): add --execute to help examples and test documented examples docs: turn the README into a landing page, and run help examples with --execute Oct 20, 2026
@thebrandonlucas thebrandonlucas added the human review wanted CI passes; ready for a human reviewer label Oct 20, 2026
@tee8z tee8z assigned tee8z and thebrandonlucas and unassigned tee8z Oct 20, 2026
@thebrandonlucas
thebrandonlucas merged commit 2de622b into master Oct 20, 2026
6 checks passed
@thebrandonlucas
thebrandonlucas deleted the docs/help-examples-execute branch October 20, 2026 12:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

human review wanted CI passes; ready for a human reviewer

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants