g1t/crates/runner/Cargo.toml

20 lines656 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.

Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)1[package]
2name = "g1t-runner"
3version = "0.1.0"
4edition.workspace = true
5license.workspace = true
GitHub Actions on g1t, part two: running workflows6description = "The program inside a g1t sandbox: runs an agent, checks, a catch-up merge, a review or a GitHub Actions job, and reports back."
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)7
8[dependencies]
GitHub Actions on g1t, part two: running workflows9g1t-actions = { path = "../actions" }
10sha2 = "0.10"
11serde_yaml = "0.9"
Deployments: a preview for every pull request, production on g1t.page12toml = "0.8"
GitHub Actions on g1t, part two: running workflows13hex = "0.4"
Account dropdown, llms.txt onboarding, hosted agent runner (not yet deployed)14anyhow = "1"
15base64 = "0.22"
16serde = { workspace = true }
17serde_json = { workspace = true }
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API18# native-certs: a guarded sandbox re-signs HTTPS with a certificate the
19# runner adds to the system store (guard.rs), which webpki-roots never sees.
20ureq = { version = "2", features = ["json", "native-certs"] }