Skip to content
⌘K
Explore
Download
Docs
Sign in
Sign up
flagon-io
/
g1t
public
Star
0
Overview
Code
Issues
8
Pull requests
3
Agents
Workflows
Deployments
Insights
Files
Commits
Branches
Tags
Releases
Compare
6c3b446ead0f65ac836c65c03798722b01cbcf18
g1t
/
services
/
events
syntaqx
A workflow job on a self-hosted runner records its sandbox time with no agent and nobody who asked, so the actions service builds again now that every sandbox line can name them.
6c3b446
1d ago
History
migrations
src
Cargo.toml
wrangler.jsonc
migrations
Merge branch 'worktree-agent-ab9543c492a7ed481' into spend-guardrails
2d ago
src
Merge branch 'mirroring' into artifacts-mode
2d ago
Cargo.toml
The docs folder is gone, and what it held lives where people read it: how a self-hosted g1t runs and how to deploy g1t to Cloudflare are pages on docs.g1t.sh under Run g1t yourself, and speed, rate limits and operating g1t.sh are sections of CONTRIBUTING.md; code that cited a file in docs/ now points to the page or section that covers it, or says what it means itself, and applied migrations and the runner images are left as they were.
1d ago
wrangler.jsonc
The artifacts service is services/artifacts, the Worker g1t-artifacts, bound as ARTIFACTS by the API, the site and the agents; its live rooms move to it with a Durable Object transfer from g1t-docs-service, and its database, bucket, indexes and queue keep their names. The git store's binding and settings are GITSTORE, its ops scripts gitstore-*, and workflow run artifacts keep their compatible API under run_artifacts modules. The deploy tool puts a Worker that has never deployed before the Workers in its stage that bind to it, and the deploy guide gives the cutover runbook.
1d ago
