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
syntaqxPages no longer blink as they refresh: a README stays put through a push, coloured diffs keep their colours, and production's picture is replaced rather than blanked. Markdown made its components for each commit (a README's pictures point at the commit shown), so every push to the branch had React take the whole README down and put it back; the components are now made once and read where links and pictures point from context, so a new commit only updates those addresses. A file in a diff (a commit, a pull request's changes, a comparison) dropped its colours on every refresh, since a refresh hands over a new file with the same lines, and drew them again when it scrolled near; it keeps them while its lines are the same. The production picture on a project's overview went back to its empty frame and "Taking a screenshot…" whenever its address changed (a new deploy) until the new one loaded; the old picture now stays under the new one until it has faded in. In Chat, every one of @g1t's answers was drawn afresh whenever a message arrived, since the repository they link into was compared as an object; it is compared by name. Router updates already run in a transition (React Router's RouterProvider wraps them in startTransition), so a refresh never shows a skeleton again once a page has loaded; that is measured below rather than changed. Checked: the site's typecheck, its 904 tests and a production build, and a harness that mounts the real routes with g1t.sh's own responses for flagon-io/g1t, decoded by React Router as the site does, watching the DOM over revalidations. Elements removed per 5 refreshes with the same data, before → after: commit page 2,495 → 0, every other page measured (overview, Code, a folder, a file, Commits, pull requests, issues, a pull request, an issue, Work, Workflows, a run, Deployments, and the same with the signed-in app shell) 0 → 0, with no skeleton shown again and no layout shift, also with deferred data taking 2.5 s. A push (a new head commit), per 4 refreshes: Code 1,077 → 0 (the README), overview's picture 18 removed and a skeleton shown → a 2-element cross-fade and none.

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.