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
- ..
- access.test.ts
- access.ts
- aliases.test.ts
- aliases.ts
- billing-actions.server.ts
- chart.test.ts
- chart.ts
- costs-route.server.ts
- costs.test.ts
- costs.ts
- credits.test.ts
- credits.ts
- deleted-accounts.test.ts
- deleted-accounts.ts
- deleted-workspaces.test.ts
- deleted-workspaces.ts
- forms.test.ts
- forms.ts
- guard.ts
- incidents.test.ts
- incidents.ts
- invites.test.ts
- invites.ts
- latency.test.ts
- latency.ts
- ledgers.test.ts
- ledgers.ts
- money.test.ts
- money.ts
- nav.test.ts
- nav.ts
- postmortem.ts
- pricing.test.ts
- pricing.ts
- review.ts
- sales-actions.server.ts
- services.server.ts
- settle.ts
- signals.test.ts
- signals.ts
- staff.ts
- suspension.test.ts
- suspension.ts
- terms.test.ts
- terms.ts
- test-detach.server.ts
- test-detach.test.ts
- test-detach.ts
- time.test.ts
- time.ts
- workspaces.test.ts
- workspaces.ts