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/…/services/actions/src

ClaudeagentMerge branch 'worktree-agent-a209db8188a251e77' into claude/cool-newton-7nm8r93d582102d agoHistory

..
cache.rs
lib.rs
managed.rs
mirrored.rs
payload.rs
plan.rs
protection.rs
reach.rs
registry.rs
rename.rs
run_artifacts.rs
runners.rs
runtime.rs
settings.rs
sync.rs
trigger.rs
views.rs

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.

..
cache.rsMerge remote-tracking branch 'origin/main' into workspace-chat5d ago
lib.rsMerge branch 'worktree-agent-a209db8188a251e77' into claude/cool-newton-7nm8r92d ago
managed.rsMerge branch 'worktree-agent-a209db8188a251e77' into claude/cool-newton-7nm8r92d ago
mirrored.rsMerge branch 'worktree-agent-a209db8188a251e77' into claude/cool-newton-7nm8r92d ago
payload.rsMerge branch 'worktree-agent-ab6bf4195fcb97f7c' into claude/cool-newton-7nm8r92d ago
plan.rsMerge branch 'worktree-agent-a209db8188a251e77' into claude/cool-newton-7nm8r92d ago
protection.rsMerge branch 'worktree-agent-a8b78c62188153aa3' into claude/cool-newton-7nm8r92d ago
reach.rsA pull request's `pull_request` runs build the pull request merged into its base branch, as on GitHub. g1t keeps `refs/pull/<number>/head` at every open pull request's head (a fork's or working copy's head commit is copied into the repository) and `refs/pull/<number>/merge` at a test merge commit of that head into the base branch's latest commit, moved whenever the head is pushed to, the pull request is opened or reopened, or its base changes; both can be fetched from the repository. A run's `github.sha` and `GITHUB_SHA` are that merge commit, `github.event.pull_request.merge_commit_sha` names it, `actions/checkout` fetches it as `+<sha>:refs/remotes/pull/<number>/merge` from the repository itself, and the workflow files and local reusable workflows are read from it; the run, its statuses and its check runs stay on the head, so required checks hold merges as before, and `pull_request_target` is unchanged. A pull request with conflicts starts no `pull_request` workflows, as on GitHub, and its checks box says why. g1t makes the merge without a sandbox, merging a file both sides changed line by line as git does; what it cannot merge itself (a rename on one side against a change on the other, more than 300 changed files) builds the head as before. The Actions and Checks guides say so.2d ago
registry.rsA workflow's `uses: actions/setup-node@v4` means GitHub's `actions` again, whoever is on g1t. g1t looked for a repository on g1t before GitHub, and anyone could make a public workspace called `actions`, `docker` or `aws-actions` and have its `setup-node` run in every workflow that names GitHub's, with that job's secrets. Now another workspace's public repository answers only for a name GitHub has no public repository of; the caller's own workspace and g1t's own `g1t/…` still answer from g1t, and when GitHub can't be asked, GitHub's is used. The names of the GitHub accounts whose actions workflows use most can no longer be registered, renamed to, or taken by signing up with GitHub (which suggests the name with `-gh`); an account that has one keeps it, and mentions and invitations still find it. The Actions, authentication and workspaces guides say so.2d ago
rename.rsMerge branch 'worktree-agent-a209db8188a251e77' into claude/cool-newton-7nm8r92d ago
run_artifacts.rsThe 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.3d ago
runners.rsMerge branch 'worktree-agent-a209db8188a251e77' into claude/cool-newton-7nm8r92d ago
runtime.rsMerge branch 'worktree-agent-af75396ad4c6ee7a8' into claude/cool-newton-7nm8r92d ago
settings.rsMerge branch 'worktree-agent-a3abfcce648e87dca'6d ago
sync.rsMerge branch 'worktree-agent-a209db8188a251e77' into claude/cool-newton-7nm8r92d ago
trigger.rsMerge branch 'worktree-agent-a209db8188a251e77' into claude/cool-newton-7nm8r92d ago
views.rsMerge branch 'worktree-agent-a209db8188a251e77' into claude/cool-newton-7nm8r92d ago