kexi/pitty-action

Run pitty PTY-based CLI testing scenarios.

Trust Signals

workflow.ymlSHA-pinned

uses: kexi/pitty@fcebd8e2334fc34ca62df5332ef21e9d40e203eb # v1.2.1

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
scenario	Path to a scenario file or a directory of scenarios.	yes	—
command	pitty subcommand to run (run, matrix, or bench).	no	run
args	Extra arguments appended to the pitty invocation.	no	""
version	pitty ref to install. Selects both the prebuilt-binary release asset (`pitty-<version>-<runner-os>-<runner-arch>.tar.gz`) and the `cargo install --git` source fallback ref. Defaults to the action ref from `uses: kexi/pitty@...`, so `@v1`, `@v1.2`, and `@v1.2.0` look for matching release assets. Set this only to intentionally install a different pitty ref than the action ref.	no	""

no outputs