syntaqxA runner release builds its three binaries side by side. Linux x64, Linux arm64 and Windows each build in a job of their own, where one job built them one after another (about six minutes each); zig and cargo-zigbuild are kept between releases rather than installed every time (four minutes); each target's build restores from the last release's when Cargo.lock has changed, and sccache brings back unchanged crates. The jobs after the build take every target's binaries, and re-running a failed job replaces what an earlier attempt uploaded.d9b1055History
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