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.
| Deployments: a preview for every pull request, production on g1t.page | 1 | { |
| 2 | "$schema": "../../node_modules/wrangler/config-schema.json", | |
| 3 | "name": "g1t-pages", | |
| 4 | "account_id": "1e6f2cffa3f445920836e8ebe446bb58", | |
| 5 | "compatibility_date": "2026-09-26", | |
| 6 | "main": "./src/index.ts", | |
| 7 | "workers_dev": false, | |
| Deploy scripts live in the repository | 8 | // Every app on g1t.page. The wildcard needs a proxied DNS record (`*`, |
| 9 | // AAAA 100::) on the zone; the apex, which says what g1t.page is, is a | |
| 10 | // custom domain, whose record Cloudflare makes. | |
| Deployments: a preview for every pull request, production on g1t.page | 11 | "routes": [ |
| 12 | { "pattern": "*.g1t.page/*", "zone_name": "g1t.page" }, | |
| Deploy scripts live in the repository | 13 | { "pattern": "g1t.page", "custom_domain": true } |
| Deployments: a preview for every pull request, production on g1t.page | 14 | ], |
| 15 | // The apps, uploaded by the deployments service. | |
| 16 | "dispatch_namespaces": [{ "binding": "APPS", "namespace": "g1t-deployments" }], | |
| 17 | "observability": { "enabled": true } | |
| 18 | } |