pome-sh/Run pome scenarios
Run pome scenarios in CI against a local twin (default) or the hosted control plane
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| scenario-path | Path to a scenario .md file (or a directory of them) in the consumer repo. | yes | — |
| pome-version | npm dist-tag or version of `pome-sh` to install. Pin in production. | no | latest |
| hosted-api-key | If non-empty, the action runs the scenario against the Pome hosted control plane (sets `POME_API_KEY` and passes `--hosted` to the CLI). If empty (default), the CLI boots a local twin in-process for the duration of the run. Source this from a repo secret, e.g. `${{ secrets.POME_API_KEY }}`. | no | "" |
| agent-command | Shell command the CLI spawns to run your agent against the twin. Forwarded to `pome run --agent <command>`. If empty, the CLI default applies — note the built-in default points at a sample path inside the `pome` repo and is not useful in a consumer workflow, so most users should set this explicitly. | no | "" |
Outputs
| name | description |
|---|---|
| result | `pass` or `fail`. |
| trace-artifact-id | GitHub Actions artifact ID for the uploaded trace directory. |