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
8a626b1639da15fcbc2b107e0902d12704a2a9bc
g1t
/
crates
/
actions
Claude
agent
Merge remote-tracking branch 'origin/main' into claude/cool-newton-7nm8r9
8a626b1
yesterday
History
..
schema
src
tests
Cargo.toml
..
schema
Merge branch 'worktree-agent-a641fa0e2e4fffccb' into claude/cool-newton-7nm8r9
yesterday
src
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.
yesterday
tests
Merge branch 'worktree-agent-a4d35ee70c50683d0' into claude/cool-newton-7nm8r9
yesterday
Cargo.toml
GitHub Actions on g1t, part one: reading workflows
1w ago