Skip to content
Sign up

flagon-io/g1t

public
00

Where people and agents ship software together. The open-source git platform for the whole job: issues, agents, checks and deploys to the edge.

gitagentscloudflarerustforgemcp
syntaqxThe g1t plugin is 0.2.8: sessions in a shared working copy no longer claim each other's files, a session started from VS Code is titled with what was typed, and files are named from the repository's root. Overlaps: every heartbeat (each turn's Stop), updates and acknowledge let the CLI report every uncommitted file in the working copy as the session's own, so several Claude Code sessions in one checkout each claimed all of them and were told they overlapped (three did on flagon-io/g1t today, editing unrelated files). The plugin now runs the CLI with G1T_TOUCH=0, and gives Claude's own shell the same through Claude Code's env file; it says what the session wrote itself: what Claude edits or writes, as before, and what a shell command changes while it runs (sed, a script, a formatter), from the uncommitted files before it (PreToolUse) and after it (PostToolUse) (dirtyFiles, shellChanges), never what was uncommitted already. Titles: VS Code puts <ide_opened_file>…</ide_opened_file> ahead of the prompt, which read as a turn Claude Code starts itself, so the session took its next prompt as its title; editor context blocks (<ide_*>, <system-reminder>) are skipped first. Paths: a file was named from Claude Code's current directory, so after cd apps/web, apps/web/app/x.ts was recorded as app/x.ts; it is named from the working copy's top (git rev-parse --show-toplevel, asked once per directory). Checked: node --test plugins/claude-code/test/hooks.test.mjs (58; new: a shell command's writes and not what was uncommitted before, no CLI call left to guess (checked after every working-copy test), IDE-prefixed titles, paths from the root); scripts/plugins-release.test.mjs (8).

README.md

g1t/deploy

Builds the checkout a g1t Actions job is in and puts it on g1t.page: production when the run is on the project's production branch, the pull request's preview for a pull request's run, and the branch's preview for a run on any other branch.

name: Deploy

on:
  push:
    branches: [main]
  pull_request:

permissions:
  contents: read
  deployments: write

jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v5
      - id: deploy
        uses: g1t/deploy@v1
      - run: echo "Live at ${{ steps.deploy.outputs.url }}"
yaml

The project must have Deployments on, and the workspace's plan must include them. The guide, Deploying from a workflow, says what is built and when.

Inputs

InputDefault
projectThe repository's one project with Deployments onThe project's slug. Needed when the repository has several.
root-dirThe project's settingWhere the project is in the checkout.
build-commandThe project's setting, else what the build findsWhat builds it.
output-dirThe project's setting, else the folder the framework writes, else the first of dist, build, out, public, _site, .output/publicThe folder a static build writes.
build-asThe project's setting, else autoWhat it is built as: auto, static, workers or docker. A container is built with the docker on the job's PATH.
dockerfileThe project's setting, else Dockerfile or ContainerfileThe Dockerfile a container is built from, relative to the project.
shaThe run's commitThe commit this is a build of, for its g1t / deploy check.
token${{ github.token }}The job's own token. It needs deployments: write; any other token is refused.

Outputs

Output
urlWhere the app is served.
deployment-idThe build's id, dpl_….
kindproduction or preview.

How it works

  1. It calls POST /repos/{owner}/{repo}/deployments/builds with the job's token. g1t checks the plan and the spend limit, decides production or preview from the run, sets the commit's g1t / deploy check to pending, and answers with a token for this build alone and the project's variables and secrets for builds of that kind.
  2. It masks that token and every secret with ::add-mask::.
  3. It runs g1t-runner deploy in the checkout, which installs, builds and uploads the app exactly as g1t's own builds do, and reports to g1t with the build's token. The build's log is in the step's.

A pull request from a fork or from someone without the Write role, and a run that had to be approved, build without the project's secrets. The build's time is the job's Actions time; it is not charged again.

g1t-runner is on g1t's machines. Elsewhere (a self-hosted runner), the action uses the one on PATH, or downloads the newest release from https://g1t.sh/downloads/runner/latest/ and checks it against the release's SHA256SUMS. It runs on Linux and macOS, with curl and either jq or python3.