Skip to content

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
16 linesCodeBlameRaw

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

Compare: any two branches, the commits one has that the other does not, and the diff, with Open a pull request1# syntax=docker/dockerfile:1.7
2#
The runner no longer runs g1t's own agents. Cloud and self-hosted runners now do what a forge's runner does: Actions jobs, required checks, merge checks and merge-queue test runs, deployments, dependency bumps and backups. Everything that started Claude Code in a sandbox on an issue or pull request is gone, with its prompts, model access, mentions, delegation, plans, reviews, revisions and the workspace agents' computers.3# The sandbox workflow jobs, g1t.page builds and g1t's own work (the merge
4# queue, merge checks, dependency updates, backups) run in: the base image
5# (services/runner/base/Dockerfile, everything but the runner) and the g1t
6# runner, a static Linux binary built outside Docker by
7# scripts/build-runner.mjs.
Compare: any two branches, the commits one has that the other does not, and the diff, with Open a pull request8#
9# Built by scripts/deploy.mjs, which passes BASE (the image recorded in
10# services/runner/base.json) and uses a build context holding only the
11# binary, so this takes seconds. docs/DEPLOYING.md explains the two images.
12
13ARG BASE
14FROM ${BASE}
15COPY --chmod=0755 g1t-runner /usr/local/bin/g1t-runner
16ENTRYPOINT ["g1t-runner"]

This file's history is long; its oldest lines are credited to the oldest commit read.