Claudeagent and ClaudeagentA workspace's owners manage its workflows under Workspace, Code, Actions: **Workflows this workspace manages** lists each with its mode, the file and commit it was copied from, the repositories it runs in and who last saved it, and **Add workflow**, **Edit**, **Copy again** and **Remove** change them, the source, mode, repositories (all, or names and patterns one per line) and visibility in one dialog; members see that only owners can. A repository's Actions page marks a workspace's workflow with the workspace's name in the list and says on its page who manages it, from which file, and whether a workflow of its name in `.g1t/workflows/` takes its place; a required one has no **Turn off**. The Actions guide has a section, Workflows a workspace manages, with the modes, targets, why the source is copied, the private-source rule, requiring its check in a ruleset, and the API, and the Workspaces guide points to it.ab407e8History
- ..
- apache_airflow.yml
- argoproj_argo-cd.yml
- aws_aws-cdk.yml
- cli_cli.yml
- cloudflare_workers-sdk.yml
- dependabot_dependabot-core.yml
- docker_compose.yml
- electron_electron.yml
- every-option.yml
- getsentry_sentry.yml
- github_docs.yml
- hashicorp_terraform.yml
- hashicorp_vault.yml
- huggingface_transformers.yml
- microsoft_TypeScript.yml
- microsoft_vscode.yml
- nodejs_node.yml
- pypa_pip.yml
- python_cpython.yml
- pytorch_pytorch.yml
- supabase_supabase.yml
- tokio-rs_tokio.yml