freckle/Stack
Build and test a stack-based Haskell project
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| working-directory | Working directory for run commands | — | — |
| test | Whether to run tests | — | true |
| color | Whether to force `--color=always` | — | true |
| stack-arguments | Additional arguments for all top-level `stack` command invocations. | — | "" |
| stack-query-arguments | Additional arguments in `stack query` invocations. | — | — |
| stack-path-arguments | Additional arguments in ``stack path`` invocations. | — | — |
| stack-setup-arguments | Additional arguments in `stack setup` invocations. | — | — |
| stack-build-arguments | Additional arguments for all `stack build` invocations. | — | --fast --pedantic |
| stack-build-arguments-dependencies | Additional arguments passed after `stack-build-arguments` in `stack build` invocations on the _Dependencies_ step. | — | — |
| stack-build-arguments-build | Additional arguments passed after `stack-build-arguments` in `stack build` invocations on the _Build_ step. | — | — |
| stack-build-arguments-test | Additional arguments passed after `stack-build-arguments` in `stack build` invocations on the _Test_ step. | — | — |
| cache-prefix | Prefix applied to all cache keys. This can be any value you like, but teams often use `v{N}` and bump it to `v{N+1}` when/if they need to explicitly bust caches. | — | — |
| cache-save-always | Save artifacts to the cache even if the build fails. This may speed up builds in subsequent runs at the expense of slightly-longer builds when a full cache-hit occurs. Since `@v4.2.0`. | — | false |
| on-dirty-files | What to do if we find changes to the cabal or lock file after a build. Value can be `warn`, or `error`. Default is `warn`. | — | warn |
| install-stack | Install stack, if necessary | — | true |
| upgrade-stack | Upgrade stack | — | true |
| compiler-tools | A list of packages to install as compiler tools, one per line. This is useful to do here rather than separate `run` commands so that their installation is incorporated in the dependency cache. Since `@v5.2.0`. | — | — |
| stack-yaml | **Deprecated** use `env.STACK_YAML` or `stack-arguments` instead. | — | — |
Outputs
no outputs