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
d512d539bcbe090958e170487564d7d84c2a89cf
g1t
/
…
/
crates
/
runner
/
src
/
actions
Claude
agent
Merge branch 'worktree-agent-a0d1a64e2033a58ed' into claude/cool-newton-7nm8r9
d512d53
yesterday
History
..
blobs.rs
containers.rs
files.rs
glob.rs
matchers.rs
mod.rs
paths.rs
process.rs
report.rs
uses.rs
zip.rs
..
blobs.rs
`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.
yesterday
containers.rs
Merge branch 'worktree-agent-ac79a505eca749d4d' into claude/cool-newton-7nm8r9
yesterday
files.rs
GitHub Actions on g1t, part two: running workflows
1w ago
glob.rs
Actions: OIDC tokens, the toolkit's cache and artifact services, and artifacts in R2
5d ago
matchers.rs
Merge branch 'worktree-agent-a41ebf64a05c894fe' into claude/cool-newton-7nm8r9
yesterday
mod.rs
Merge branch 'worktree-agent-a1eb74e8a85291bbb' into claude/cool-newton-7nm8r9
yesterday
paths.rs
Fast pages, required checks on the branch, self-hosted runners, honest incidents
1w ago
process.rs
A running job's log is live, as on GitHub. A step's output reaches its run's page within about two seconds: the runner sends what is printed every second, and the page asks every second while a step runs, every three while none does; an answer that fails (a 429, a 5xx, the network) is asked again after a wait that doubles to half a minute, or as long as Retry-After says, where before one such answer stopped the log for good and the step said "No output yet." until the page was reloaded, and a signed-out viewer's run page, refreshing beside its log, ran into the 30-a-minute limit within a minute; the live log now counts as a page, and only log downloads as costly. A hidden tab stops asking and catches up when shown, and the page says when it is reconnecting. The running step opens by itself, its timer counts, its log follows the newest line while its end is on screen and offers Jump to latest once the viewer scrolls up, a step that has printed nothing for a while says "Running · no output for 2m 10s", and the job's header names the step it is on. Colour that tools print (bold, dim, italic, underline, the 16 colours as theme tokens for light and dark, 256 colours and 24-bit colour, text and background) is drawn as printed, other escape codes are dropped and links keep their text, and search reads the plain text and keeps the colours around what it marks. Every line is stamped with the time it was printed, as GitHub's raw logs are, so log.txt and the run's zip have a time at the start of each line, and a clock button beside Search logs shows the times, remembered by the browser. Set up job now gives the runner's version and name, the operating system, the runner image, the machine's architecture, CPUs and memory, the token's permissions under G1T_TOKEN Permissions, the secret source and the actions it downloads; each run step opens with GitHub's folded Run group, the script in cyan, the shell's whole path and the step's env, each uses step with its with inputs (an action's defaults among them) and env; cache and artifact transfers say how far they have got every five seconds; and a last Complete job step sets the job's outputs and stops what the steps left running, found by RUNNER_TRACKING_ID as GitHub's runner finds it. Two batches of a job's log written at once can no longer reach for the same seq and lose one. The Actions guide and the rate limits page say so.
yesterday
report.rs
Merge branch 'worktree-agent-a39a116f38472effe' into claude/cool-newton-7nm8r9
yesterday
uses.rs
`actions/checkout` is the real action now, at the version a step names: g1t's runner no longer checks out in its place. It fetches from g1t with the job's token, as on GitHub, including a pull request's test merge commit, which g1t now keeps in the repository as `refs/pull/<number>/merge` beside `refs/pull/<number>/head`, and its post step removes the credential it left. Every input and output is the action's own. In a job container whose image has no git, the action falls back to a tarball download g1t does not serve yet, and `lfs` finds no files: the limitations say so, with what to do instead.
yesterday
zip.rs
Actions: OIDC tokens, the toolkit's cache and artifact services, and artifacts in R2
5d ago