Claudeagent and Claudeagent`actions/cache`, `actions/cache/restore` and `actions/cache/save` are the real actions now, at the version a step names, as `setup-node` and every other action are: g1t's runner no longer stands in for them by name. They save to and restore from the repository's cache through the toolkit's cache service, which g1t already answered, so an entry `actions/cache` saves is restored by `setup-node` with the same key and paths, and the other way round, as on GitHub. Entries the stand-in saved were versioned its own way and are not restored by the real action: each cache misses once, then fills again. As for every toolkit cache, an entry between 100 and 128 MB, which the toolkit sends in one request, is not saved. The Actions guide and the limitations say so.fdde3acHistory
README.md
g1t/workflows
g1t's own reusable workflows, published from this folder of g1t's
repository to g1t/workflows on g1t.sh by .g1t/workflows/actions-release.yml.
| Workflow | What it does |
|---|---|
.g1t/workflows/deploy.yml | Builds the commit onto g1t.page with g1t/deploy. The deploy workflow g1t manages for a project calls it. |
jobs:
g1t:
uses: g1t/workflows/.g1t/workflows/deploy.yml@v1
with:
project: web
secrets: inherityaml