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
- ..
- about.rs
- addresses.rs
- alerts.rs
- audit.rs
- billing.rs
- blobs.rs
- checks.rs
- deploy_keys.rs
- deployments.rs
- folios.rs
- lib.rs
- limits.rs
- logs.rs
- mcp.rs
- mirrors.rs
- notifications.rs
- oauth.rs
- oidc.rs
- openapi.rs
- operations.rs
- packages.rs
- people.rs
- pins.rs
- projects.rs
- protection.rs
- reference.json
- renamed.rs
- responses.rs
- rest.rs
- rules.rs
- run_artifacts.rs
- runners.rs
- security.rs
- token_policy.rs
- toolkit.rs
- tools.rs