flagon-io/g1t

public

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/services/work/wrangler.jsonc

30 lines1,009 bytesCodeBlame

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.

Initial g1t: services, event bus, intents and attempts1{
2 "$schema": "../../node_modules/wrangler/config-schema.json",
3 "name": "g1t-work",
4 "account_id": "1e6f2cffa3f445920836e8ebe446bb58",
5 "compatibility_date": "2026-09-26",
Agents as a team: lifecycle, merge queue, billing and a new shell6 // Runs next to its database: a request makes several queries in turn,
7 // and each would otherwise cross the distance to it.
Fast pages, required checks on the branch, self-hosted runners, honest incidents8 "placement": { "mode": "off" },
Work service in Rust, with RFC 3339 timestamps9 "main": "build/index.js",
Deploys as code: a manifest of every Worker, a deploy tool that ships only what changed in parallel stages, and a g1t Actions workflow10 "build": { "command": "node ../../scripts/build-rust-worker.mjs" },
Initial g1t: services, event bus, intents and attempts11 "workers_dev": false,
12 "d1_databases": [
13 {
14 "binding": "DB",
15 "database_name": "g1t-work",
16 "database_id": "f35a9022-e36b-4547-b596-9ab9d5f1c47a",
17 "migrations_dir": "migrations"
18 }
19 ],
20 "services": [
Agents as a team: lifecycle, merge queue, billing and a new shell21 { "binding": "IDENTITY", "service": "g1t-identity" },
Initial g1t: services, event bus, intents and attempts22 { "binding": "REPOS", "service": "g1t-repos" },
Sidebar: the panels really slide23 { "binding": "EVENTS", "service": "g1t-events" },
24 { "binding": "ACTIONS", "service": "g1t-actions" }
Initial g1t: services, event bus, intents and attempts25 ],
26 "queues": {
27 "consumers": [{ "queue": "g1t-events-work", "max_batch_size": 100, "max_batch_timeout": 1 }]
28 },
29 "observability": { "enabled": true }
30}