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
- ..
- notify
- repo
- settings
- workspace
- auth-github-callback.tsx
- auth-github-username.tsx
- auth-github.ts
- avatar-user.ts
- confirm-email.tsx
- desktop-runner.ts
- device.tsx
- download.tsx
- downloads-runner.ts
- explore.tsx
- forgot.tsx
- github-install.ts
- github-setup.tsx
- home.tsx
- hovercard-user.ts
- inbox-json.ts
- inbox-moved.ts
- install-script.ts
- invitations.tsx
- invite.tsx
- login-two-factor.tsx
- login.tsx
- logout.tsx
- new-github.tsx
- new.tsx
- not-found.tsx
- notifications.tsx
- oauth-authorize.tsx
- people-json.ts
- policies.tsx
- policy.tsx
- pricing.tsx
- register.tsx
- reset.tsx
- robots-txt.ts
- search-json.ts
- search.tsx
- security-txt.ts
- security.tsx
- settings-menu-json.ts
- sitemap-xml.ts
- status-json.ts
- status.tsx
- support.tsx
- user.tsx
- verify.tsx
- well-known-g1t.ts