Claudeagent and Claudeagentg1t has actions of its own: g1t/deploy builds the checkout a job is in and puts it on g1t.page, opening the build with the job's token, masking the build's token and the project's secrets, and running g1t-runner deploy, with the app's url, the deployment's id and its kind as outputs; g1t/detect says what such a build would find (kind, install, build and output-dir) without building anything. Both use the g1t-runner on the machine, or download the newest release from g1t.sh/downloads/runner and check it against its SHA256SUMS. They live under actions/, and the Actions release workflow pushes each folder to its own repository in the g1t workspace and moves its v1 tag whenever main changes them, with the G1T_ACTIONS_PUBLISH_TOKEN secret its header describes.6a4dc3fHistory
- ..
- abuse.tsx
- agents.tsx
- aliases.tsx
- audit.tsx
- costs-bill.tsx
- costs.tsx
- credits.tsx
- deleted-accounts.tsx
- deleted-workspaces.tsx
- enterprise.tsx
- enterprises.tsx
- incident-new.tsx
- incident-postmortem.tsx
- incident.tsx
- incidents.tsx
- invites.tsx
- invoices.tsx
- legacy-accounts.tsx
- maintenance-new.tsx
- maintenance.tsx
- new-enterprise.tsx
- overages.tsx
- overview.tsx
- reach-out.tsx
- requests.tsx
- soon.tsx
- stripe.tsx
- timezone.tsx
- user.tsx
- velocity.tsx
- workspace.tsx
- workspaces.tsx