andriiklymiuk/Setup corgi
Install corgi from a verified release archive and expose what a CI cache should persist.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| version | corgi version to install, without the leading v (e.g. 1.20.13). Omit to take the latest release. Pinning keeps a workflow reproducible. | no | "" |
| working-directory | Directory holding corgi-compose.yml. Cache outputs are derived from it. | no | . |
Outputs
| name | description |
|---|---|
| version | The corgi version that was installed. |
| cache-paths | Newline-separated directories worth caching, derived from every service's beforeStart cacheKey. Pass straight to actions/cache's path input. |
| cache-key | Cache key that changes whenever any cacheKey file changes. Pass straight to actions/cache's key input. |
| cache-groups | The same plan split per ecosystem, as JSON: a list of {id, key, paths, pathsText}. One actions/cache step per entry keeps a change to one language's lockfile from evicting every other language's packages. pathsText is newline-joined because an Actions expression cannot build that string itself. |