syntaqxWhether a repository's Actions are on is read once per request, however many runs it starts. actions_on read repo_settings in D1 in each trigger path and again in create_run for every run, so one push starting five workflows read it six times. The service now keeps what it read in ActionsOn (protection.rs), a per-request map of repository id to on or off: the service is made afresh for each fetch and for the minute's sweep, Actions::on_event clears it for each queued event, and saving a repository's Actions settings forgets that repository's entry. create_run stays the gate for every trigger (push, pull_request including a fork's, merge_group, schedule, workflow_run, dispatch and the rest), and record_failed_run, which now takes the repository, is gated the same way, so an unreadable workflow file in a repository with Actions off records nothing. on_event, run_schedules and merge_group still ask before reading workflows from git or a schedule's head, now from the same read; dispatch, repository_dispatch and re-run still refuse with the same message. Behaviour is unchanged.0c9ad8cHistory
- ..
- 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
- 0018_desktop_runners.sql
- 0019_brokered_secrets.sql
- 0020_job_token_rotation.sql
- 0021_log_retention.sql
- 0022_runner_machine.sql
- 0023_actions_enabled.sql