Skip to content

docs: fix export-bash-scripts flag from --out to --output #2148

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

docs: fix export-bash-scripts flag from --out to --output #2148

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion AGENTS.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions docs/extending.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down