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.
| Rust repos service with shipping; pull requests kept in the model | 1 | [package] |
| 2 | name = "g1t-repos" | |
| 3 | version = "0.1.0" | |
| 4 | edition.workspace = true | |
| 5 | license.workspace = true | |
| 6 | description = "Repository registry, contents, forks, landing and git over HTTPS." | |
| 7 | ||
| 8 | [lib] | |
| 9 | crate-type = ["cdylib"] | |
| 10 | ||
| 11 | [dependencies] | |
| 12 | g1t-contracts.workspace = true | |
| 13 | g1t-kit.workspace = true | |
| Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API | 14 | g1t-scan.workspace = true |
| Mission control shows where you are needed and what agents landed without you; git answers in about 200ms | 15 | g1t-secrets.workspace = true |
| Rust repos service with shipping; pull requests kept in the model | 16 | serde.workspace = true |
| 17 | serde_json.workspace = true | |
| 18 | worker.workspace = true | |
| Agents as a team: lifecycle, merge queue, billing and a new shell | 19 | futures-util = { version = "0.3", default-features = false, features = ["alloc"] } |
| Diffs on attempts; hosted agent presented as the g1t agent | 20 | similar = "2" |
| Deploys as code: a manifest of every Worker, a deploy tool that ships only what changed in parallel stages, and a g1t Actions workflow | 21 | |
| 22 | # wasm-opt at -O1: about the same gzipped size as -O in a tenth of the | |
| 23 | # time (docs/DEPLOYING.md, "Build speed"). | |
| 24 | [package.metadata.wasm-pack.profile.release] | |
| 25 | wasm-opt = ["-O1"] |