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
syntaqxA session's transcript reads as what it said, with its tool calls between: "What it recorded" on a session's page (and What happened on a pull request's Session tab) drew every entry as a full-height row. A tool call said its tool twice ("bash bash: curl …", "g1t:issue g1t:issue: work"), a message's Markdown showed its ** and backticks as written, the prompt's <issue> and <comment> blocks were raw text in a <pre>, and a run of eight tool calls was eight bordered rows. Tool calls between two messages now run together (lib/session-entries.ts transcript): up to three in a tight list, more folded into one line ("7 tool calls · bash, write, read") that opens to it, each result folded under the call before it. Each call says its tool once (readToolCall takes the "<tool>: " off the front of its text, and finds the tool in the text when the entry has none, as from the Claude Code plugin): a command as code in one line, a long one unfolding in full; a file by its path with a file icon; an MCP tool by resource and action ("issue · claim", "pull request · create") with the g1t mark for g1t's, and its server's name for others (mcp__claude_ai_Google_Drive__… is Google Drive). Messages render with the site's Markdown, references linked within the repository. The prompt folds under its first line and opens to it rendered, its <issue> and <comment> blocks as quotes under a label (quotedBlocks). Relative times stay on prompts, messages, skills and notes. The sessions guide says how the transcript reads.

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.