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
24 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.

status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas1[package]
2name = "g1t-api"
3version = "0.1.0"
4edition.workspace = true
5license.workspace = true
6description = "The REST API and MCP server."
7
8[lib]
9crate-type = ["cdylib"]
10
11[dependencies]
12g1t-contracts.workspace = true
13g1t-kit.workspace = true
14serde.workspace = true
15serde_json = { workspace = true, features = ["preserve_order"] }
16worker.workspace = true
17base64 = "0.22"
Actions: OIDC tokens, the toolkit's cache and artifact services, and artifacts in R218sha2 = "0.10"
status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas19form_urlencoded = "1"
Deploys as code: a manifest of every Worker, a deploy tool that ships only what changed in parallel stages, and a g1t Actions workflow20
21# wasm-opt at -O1: about the same gzipped size as -O in a tenth of the
The docs folder is gone, and what it held lives where people read it: how a self-hosted g1t runs and how to deploy g1t to Cloudflare are pages on docs.g1t.sh under Run g1t yourself, and speed, rate limits and operating g1t.sh are sections of CONTRIBUTING.md; code that cited a file in docs/ now points to the page or section that covers it, or says what it means itself, and applied migrations and the runner images are left as they were.22# time.
Deploys as code: a manifest of every Worker, a deploy tool that ships only what changed in parallel stages, and a g1t Actions workflow23[package.metadata.wasm-pack.profile.release]
24wasm-opt = ["-O1"]

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