g1t/services/repos/wrangler.jsonc

57 lines2,655 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-repos",
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.
8 "placement": { "mode": "smart" },
Rust repos service with shipping; pull requests kept in the model9 "main": "build/index.js",
10 "build": { "command": "cargo install -q worker-build@0.8.7 && worker-build --release" },
Initial g1t: services, event bus, intents and attempts11 "workers_dev": false,
12 "d1_databases": [
13 {
14 "binding": "DB",
15 "database_name": "g1t-repos",
16 "database_id": "f9544c51-c3bf-4621-a96f-8a6d5cf24a97",
17 "migrations_dir": "migrations"
18 }
19 ],
20 "artifacts": [{ "binding": "ARTIFACTS", "namespace": "g1t" }],
Mission control shows where you are needed and what agents landed without you; git answers in about 200ms21 // Shared between isolates (src/shared.rs): the git store's credentials
22 // (src/store.rs) and the ref listings git asks for first
23 // (src/refs_cache.rs), every value sealed with the REPOS_KEY secret (64
24 // hex characters). Without the binding or the secret each isolate keeps
25 // only its own. Made by `npx wrangler kv namespace create g1t-repos-git-cache`:
26 "kv_namespaces": [{ "binding": "GIT_CACHE", "id": "be765052d0124c2a935b3db4dff99f1f" }],
Initial g1t: services, event bus, intents and attempts27 "services": [
28 { "binding": "IDENTITY", "service": "g1t-identity" },
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API29 { "binding": "EVENTS", "service": "g1t-events" },
30 // Push protection asks which secrets were allowed, and records the rest.
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look31 { "binding": "SECURITY", "service": "g1t-security" },
32 // Whether a workspace far past its free git operations is on the
33 // plan (src/git_ops.rs); asked only then.
34 { "binding": "BILLING", "service": "g1t-billing" }
Initial g1t: services, event bus, intents and attempts35 ],
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look36 // A free workspace past this many git operations in a month is slowed
status.g1t.sh with incident management, invites that land you in the workspace, settings as pages, usage without quotas37 // to this many an hour, never charged (src/git_ops.rs). It is billing's
38 // GIT_OPERATIONS_INCLUDED, the amount free for every workspace: past it,
39 // a workspace on the plan pays at cost plus 20% and is never slowed.
Invite-only launch: sign in with GitHub, repository access and lifecycle, many emails, a new look40 // FREE_PRIVATE_STORAGE_BYTES: a free workspace's private repositories may
41 // hold this much (1 GB); past it, pushes to them stop. Billing reads the
42 // same amount.
43 "vars": {
44 "GIT_OPERATIONS_FREE_CAP": "50000",
45 "GIT_OPERATIONS_FREE_HOURLY": "60",
46 "FREE_PRIVATE_STORAGE_BYTES": "1000000000"
47 },
48 // Every hour, deleted repositories whose 30 days to be restored have
49 // passed are purged, their git data with them (src/lifecycle.rs).
50 "triggers": { "crons": ["23 * * * *"] },
51 // A workspace renamed moves its repositories to the new slug; one
52 // deleted purges the repositories it left in Recently deleted.
Agents and memory, checks and conflicts, profiles, slug renames, custom domains53 "queues": {
54 "consumers": [{ "queue": "g1t-events-repos", "max_batch_size": 20, "max_batch_timeout": 1 }]
55 },
Initial g1t: services, event bus, intents and attempts56 "observability": { "enabled": true }
57}