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
eb2bf6df99c97d5415deb5e494663c870389a640
g1t
/
services
/
deployments
syntaqx
Merge branch 'worktree-agent-a5c94df323642630e'
eb2bf6d
1d ago
History
..
migrations
src
package.json
tsconfig.json
wrangler.jsonc
..
migrations
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.
1d ago
src
Merge remote-tracking branch 'origin/claude/cool-newton-7nm8r9' into claude/cool-newton-7nm8r9
1d ago
package.json
status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas
7d ago
tsconfig.json
Deployments: a preview for every pull request, production on g1t.page
8d ago
wrangler.jsonc
Merge branch 'worktree-agent-a8752162fea25f63f' into spend-guardrails
4d ago
