Claudeagent and ClaudeagentA repository can run a managed workflow: one installed by g1t's own services without a file in the repository. It is listed, started, run and re-run like any workflow in `.g1t/workflows/`, under the path `managed/<name>.yml`, and a workflow of the same `name:` in the repository runs in its place, so moving one into the repository is committing its source. The Actions page says a managed workflow is managed by g1t rather than linking to a file. Nothing installs one yet; the deploy workflow deployments will install, which calls g1t's reusable deploy workflow with a project's settings as its inputs and reports as `g1t / deploy`, is written and tested but not installed.ef6c4dcHistory
- ..
- 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