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.

g1t.sh
gitagentscloudflarerustforgemcp
syntaqxThe site shows who is working on what: a repository's Work page, an issue's Work panel, a pull request's integration failure and decisions, and why-blame's decisions. The Work page (/<workspace>/<repo>/work, a tab beside Pull requests, Merge queue and Sessions) lists Live now, the active claims and the active and idle harness sessions grouped by issue, with an issue claimed twice marked; the merge queue's train; What happened, the latest 30 coordination events as a feed; and Just landed, the latest merges with a link to the session behind each. With nothing going on it says how to start: the Claude Code plugin's two commands, or g1t work claim from any harness. An issue's sidebar opens with a Work panel: its claims (who, which harness, since when, when each lapses, and ones released, expired or handed off lately dimmed), its sessions with their state and when each was last heard from, what it is blocked by and where each stands, and what it blocks; its author and Triage change blocked_by with Edit, through update_issue. Under its pull requests the issue shows the latest combination that failed in the merge queue (the pull requests tested together, the failing check linked to its run, what it fails with, and the fix or pass that answered it) and its decision records, each badged Claimed, Tested or Approved. A pull request shows that failure above its checks until it passes in the queue or merges, and its Session tab lists the harness sessions on it and its decisions above what was recorded. A session has a page of its own at work/sessions/<id>. Why-blame's panel adds How it was decided: the failed combination and its fix, then the proposals, the approval and the merge, from the decisions on the issue and all its pull requests.

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.