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
- ..
- 0001_init.sql
- 0002_reusable_workflows.sql
- 0003_settings_access.sql
- 0004_self_hosted_runners.sql
- 0005_actions_cache.sql
- 0006_artifacts.sql
- 0007_run_protection.sql
- 0008_actions_access.sql
- 0009_run_attempts.sql
- 0010_jobs_self_hosted_lower.sql
- 0011_schedule_rules.sql
- 0012_runner_task_runs.sql
- 0013_action_registry.sql
- 0014_managed_workflows.sql
- 0015_runner_isolation.sql
- 0016_log_chunks.sql
- 0017_workspace_managed_workflows.sql