From c9a46c15038f0667361b0681880449bb9b7f5fe5 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sat, 12 Sep 2026 08:40:00 +0000 Subject: [PATCH] docs: fix export-bash-scripts flag from --out to --output The clap CLI defines the export-bash-scripts output path as --output/-o (src/main.rs Commands::ExportBashScripts), not --out. AGENTS.md and docs/extending.md examples used --out, which fails with an unrecognized-argument error if copy-pasted since clap does not have short/long flag inference enabled. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- AGENTS.md | 2 +- docs/extending.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 9f231c07..ed2868ca 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -623,7 +623,7 @@ the directive and it's inert at runtime. To review the generated shell as ordinary files: ```bash -cargo run -- export-bash-scripts --out /tmp/ado-aw-shell +cargo run -- export-bash-scripts --output /tmp/ado-aw-shell ``` ### Markdown-only smoke suite diff --git a/docs/extending.md b/docs/extending.md index 7a84e95d..af573ae0 100644 --- a/docs/extending.md +++ b/docs/extending.md @@ -457,8 +457,8 @@ ShellScript::new(&START_CONTAINER) ### Reviewing the scripts as files ```bash -cargo run -- export-bash-scripts --out /tmp/ado-aw-shell -cargo run -- export-bash-scripts --out /tmp/ado-aw-shell --format json +cargo run -- export-bash-scripts --output /tmp/ado-aw-shell +cargo run -- export-bash-scripts --output /tmp/ado-aw-shell --format json ``` Writes one `.sh` per registered script with a provenance header naming the