Skip to content

⌘K

Explore Download Docs

flagon-io/g1t

public

Overview Code Issues Pull requests Workflows Deployments Insights

Files Commits Branches Tags Releases Compare

g1t/.g1t/workflows

syntaqxMerge branch 'worktree-agent-a63425cb2d4935c5f'6f03f2cyesterdayHistory

..
actions-release.yml
caches.yml
ci.yml
cli-release.yml
conformance.yml
deploy.yml
desktop-release.yml
mobile-build.yml
mobile-release.yml
runner-base.yml
runner-release.yml

Where your team and its coding agents ship code.

Product

Explore
Pricing
Download
Chat
Bring your own agent
Integrations

Developers

Documentation
API reference
MCP tools
llms.txt

Company

Flagon, Inc.
Support
Security
Status

Open source

Source on g1t
MIT license
Run g1t yourself

g1t is designed, built, and backed by Flagon, Inc., a small, independent software company founded by Chase Pierce.

Checking statusStatus
Support
Policies
Privacy
Security

·

Sign in
© 2026 Flagon, Inc. All rights reserved.

..
actions-release.ymlThe Actions release pushes with its publish token alone. actions/checkout left the job's own token in git's config for g1t.sh, so each push sent it beside the publish token, and g1t took the job's, which may only write this repository: the release created g1t/deploy and was then refused pushing to it. The checkout keeps no credentials now.yesterday
caches.ymlMerge branch 'worktree-agent-a63425cb2d4935c5f'yesterday
ci.ymlMerge branch 'worktree-agent-a63425cb2d4935c5f'yesterday
cli-release.ymlEvery install in g1t's workflows and deploy tool goes through scripts/deploy/npm-ci.mjs, which runs npm ci again when a connection drops: npm does not retry a body that breaks off midway, so an ECONNRESET or network aborted, an install that ends without saying why, or one that prints nothing for 12 minutes is tried again, up to three times; a real error, such as a lockfile out of step, still fails at once. A test keeps every workflow on it.yesterday
conformance.ymlsuccess(), failure(), cancelled() and always() work only in an if:, as on GitHub. Anywhere else, such as a step's env, g1t now refuses them with GitHub's own error, "Unrecognized function: 'success'"; before, g1t accepted them everywhere, and the Conformance workflow, which read success() in its env, ran on g1t and failed on GitHub. The workflow no longer reports it, and the Actions guide says where the status functions may be called.yesterday
deploy.ymlMerge branch 'worktree-agent-a63425cb2d4935c5f'yesterday
desktop-release.ymlMerge branch 'worktree-agent-a63425cb2d4935c5f'yesterday
mobile-build.ymlEvery install in g1t's workflows and deploy tool goes through scripts/deploy/npm-ci.mjs, which runs npm ci again when a connection drops: npm does not retry a body that breaks off midway, so an ECONNRESET or network aborted, an install that ends without saying why, or one that prints nothing for 12 minutes is tried again, up to three times; a real error, such as a lockfile out of step, still fails at once. A test keeps every workflow on it.yesterday
mobile-release.ymlEvery install in g1t's workflows and deploy tool goes through scripts/deploy/npm-ci.mjs, which runs npm ci again when a connection drops: npm does not retry a body that breaks off midway, so an ECONNRESET or network aborted, an install that ends without saying why, or one that prints nothing for 12 minutes is tried again, up to three times; a real error, such as a lockfile out of step, still fails at once. A test keeps every workflow on it.yesterday
runner-base.ymlEvery install in g1t's workflows and deploy tool goes through scripts/deploy/npm-ci.mjs, which runs npm ci again when a connection drops: npm does not retry a body that breaks off midway, so an ECONNRESET or network aborted, an install that ends without saying why, or one that prints nothing for 12 minutes is tried again, up to three times; a real error, such as a lockfile out of step, still fails at once. A test keeps every workflow on it.yesterday
runner-release.ymlMerge branch 'worktree-agent-a63425cb2d4935c5f'yesterday