Skip to content
⌘K
Explore
Download
Docs
Sign in
Sign up
flagon-io
/
g1t
public
Star
0
Overview
Code
Issues
Pull requests
Agents
Workflows
Deployments
Insights
Files
Commits
Branches
Tags
Releases
Compare
8a626b1639da15fcbc2b107e0902d12704a2a9bc
g1t
/
crates
Claude
agent
Merge remote-tracking branch 'origin/main' into claude/cool-newton-7nm8r9
8a626b1
17h ago
History
actions
blobstore
contracts
g1t
kit
rules
runner
scan
secrets
sshd
actions
A project can build with a workflow. Turning on **Build with a workflow** under Settings, Deployments installs a managed workflow named `g1t` that calls g1t's reusable deploy workflow (`g1t/workflows/.g1t/workflows/deploy.yml@v1`, published from `workflows/` by the actions release) with the project's settings, and pushes and pull requests then start it rather than a build of Deployments' own: the same previews and production, at the same addresses, reported as `g1t / deploy`, now the check of the workflow's job, listed on the Actions page with its runs and logs. A pull request from a fork runs it with a read-only token, as on GitHub, and still gets its preview without the project's build secrets: a read-only job token may open a preview build only from a run of a managed workflow. Fork pull requests run the repository's managed workflows too. Its jobs are Actions time, at cost plus 20% on g1t's machines and free on a self-hosted runner. A workflow named `g1t` in `.g1t/workflows/` takes its place. The deployments and Actions guides say so.
18h ago
blobstore
Merge branch 'worktree-agent-af58ac8933b0dd125'
5d ago
contracts
Merge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r9
17h ago
g1t
g1t push: images with layers of any size, uploaded in chunks under the edge's limit
5d ago
kit
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.
2d ago
rules
Merge checks: statuses and check runs on every commit
4d ago
runner
The self-hosted runner is 0.2.1: it sends a running job's log every second with a timestamp on every line, opens each step with GitHub's `Run …` group (the script, its shell and `env:`), lists the machine, image and token permissions under Set up job, reports progress through long cache and artifact transfers, and ends with a Complete job step that sets the job's outputs and stops processes the steps left running. Runners update themselves to it.
17h ago
scan
A push is checked once and side by side: its pack is read and its bases fetched once for the rules, the workflow gate and the secret scan, which run together, other services are asked while the pack is read, and cache writes and rule records finish after git has its answer
3d ago
secrets
Mission control shows where you are needed and what agents landed without you; git answers in about 200ms
6d ago
sshd
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.
2d ago