syntaqxThe desktop app runs a self-hosted runner for the signed-in person, a few seconds after its window opens, and stops it when g1t quits. It is on unless turned off in settings, runs sandboxed by default, and never falls back to anything that is not a sandbox: on Linux with Sysbox it is the runner's image under sysbox-runc, with no Docker socket; elsewhere it says a sandbox isn't available on this computer yet and runs nothing, until g1t-runner's sandbox launcher is released, which one small module (runner/launcher.rs) will call. Running jobs in Docker, or directly on this computer, are choices a person makes, each said plainly for what it can reach.fc04f29History
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