syntaqxA runner release publishes its sandbox images again. Each build job caches its target folder between releases, and that brought back the last release's target/runner-release/0.3.0 beside the new version's, so both went up in the job's files: the container image job's `cp release/*/g1t-runner-linux-x64` found two programs and stopped, the sandbox images were skipped after it, and 0.3.1 went out signed but without its sandbox section, so a computer setting up the sandbox for the first time waits for images. The build jobs now start from an empty target/runner-release, and the image and sandbox jobs name the version's own folder rather than a wildcard.6cd2cc0History
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