syntaqxThe g1t CLI is 0.3.5 and trusts the system's certificate store: in a Claude Managed Agents sandbox, which re-signs HTTPS with a proxy certificate it adds to /etc/ssl/certs, every g1t command failed TLS verification (the CLI trusted only the webpki-roots list built into it), so sessions gave up on the CLI and fell back to MCP tools and plain git ("The CLI can't verify the sandbox's TLS proxy"). ureq now has native-certs, as g1t-runner already does for guarded sandboxes. The CLI guide says so under Behind a TLS proxy. Checked: cargo test -p g1t (109 and 51).25309b9History
README.md
g1t/workflows
g1t's own reusable workflows, published from this folder of g1t's
repository to g1t/workflows on g1t.sh by .g1t/workflows/actions-release.yml.
| Workflow | What it does |
|---|---|
.g1t/workflows/deploy.yml | Builds the commit onto g1t.page with g1t/deploy. The deploy workflow g1t manages for a project calls it. |
jobs:
g1t:
uses: g1t/workflows/.g1t/workflows/deploy.yml@v1
with:
project: web
secrets: inherityaml