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.
| Agents move along on private repositories too | 1 | [package] |
| 2 | name = "g1t-integrations" | |
| 3 | version = "0.1.0" | |
| 4 | edition.workspace = true | |
| 5 | license.workspace = true | |
| 6 | description = "A workspace's connections to systems outside g1t: model providers, alerts and trackers." | |
| 7 | ||
| 8 | [lib] | |
| 9 | crate-type = ["cdylib"] | |
| 10 | ||
| 11 | [dependencies] | |
| 12 | g1t-contracts.workspace = true | |
| 13 | g1t-kit.workspace = true | |
| 14 | g1t-secrets.workspace = true | |
| 15 | serde.workspace = true | |
| 16 | serde_json.workspace = true | |
| 17 | worker.workspace = true | |
| 18 | base64 = "0.22" | |
| 19 | getrandom = { version = "0.2", features = ["js"] } | |
| 20 | hex = "0.4" | |
| 21 | sha2 = "0.10" | |
| Deploys as code: a manifest of every Worker, a deploy tool that ships only what changed in parallel stages, and a g1t Actions workflow | 22 | |
| 23 | # 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. | 24 | # time. |
| Deploys as code: a manifest of every Worker, a deploy tool that ships only what changed in parallel stages, and a g1t Actions workflow | 25 | [package.metadata.wasm-pack.profile.release] |
| 26 | wasm-opt = ["-O1"] |
This file's history is long; its oldest lines are credited to the oldest commit read.