Skip to content
⌘K
Explore
Download
Docs
Sign in
Sign up
flagon-io
/
g1t
public
Star
0
Overview
Code
Issues
Pull requests
Workflows
Deployments
Insights
Files
Commits
Branches
Tags
Releases
Compare
dbb4e2d5f47de76491e7b9144c5ac5766436a2f9
g1t
/
.g1t
/
workflows
syntaqx
The sandbox's VM image builds. It enabled systemd-resolved, which Debian 12 ships in a package of its own that the image did not install, so the runner release's sandbox images stopped at that step; it installs it now.
dbb4e2d
yesterday
History
..
actions-release.yml
ci.yml
conformance.yml
deploy.yml
desktop-release.yml
mobile-release.yml
runner-base.yml
runner-release.yml
..
actions-release.yml
The Actions release reads its token from ACTIONS_PUBLISH_TOKEN. It asked for G1T_ACTIONS_PUBLISH_TOKEN, a name g1t keeps for its own and refuses when a secret is saved, so the secret it needed could never be set. A test now fails any of g1t's workflows that reads a secret named G1T_ or GITHUB_ other than the job's own token.
yesterday
ci.yml
Merge remote-tracking branch 'origin/claude/cool-newton-7nm8r9'
yesterday
conformance.yml
Merge remote-tracking branch 'origin/claude/cool-newton-7nm8r9'
yesterday
deploy.yml
The deploy's stages ride out a dropped npm connection as CI does. Each core, edge and front job keeps npm's downloads between runs (actions/cache on ~/.npm, keyed on the lockfile), and the deploy tool's install reads them first (npm ci --prefer-offline), so a registry connection reset mid-install no longer fails a stage, as it failed the web stage of Deploy 201.
yesterday
desktop-release.yml
The Windows installer builds on Linux. Tauri's installer script includes Win\RestartManager.nsh, which NSIS ships from 3.10 on, and Debian's NSIS is 3.08, so makensis stopped at it; the job adds that one header from NSIS 3.11's source, checked against its SHA-256.
yesterday
mobile-release.yml
Releases no longer show as deploys of g1t.sh. The runner, runner image, desktop and phone release jobs read production's secrets without making a deployment (environment with deployment: false, as the deploy's plan job does), so a release in progress no longer puts 'Building' and its tag's commit on the project's production card.
yesterday
runner-base.yml
Releases no longer show as deploys of g1t.sh. The runner, runner image, desktop and phone release jobs read production's secrets without making a deployment (environment with deployment: false, as the deploy's plan job does), so a release in progress no longer puts 'Building' and its tag's commit on the project's production card.
yesterday
runner-release.yml
A 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.
yesterday
