Deploy automatically from a GitHub repository on Deno Deploy (push-to-deploy)

Documented steps

1. Auth: Authorize the Deno Deploy GitHub App for the account/org from the repo dropdown in console.deno.com; CLI auth is separate (keyring token via browser login).
2. In console.deno.com click + New App, or run: deno deploy create --org my-org --app my-app --source github --owner my-github-org --repo my-repo --framework-preset astro --build-timeout 10 --build-memory-limit 2048.
3. If the repo isn't listed, click + Add another GitHub account to authorize the Deno Deploy GitHub App for it.
4. Set build config (entrypoint, optional install/build commands) via dashboard fields or deno.json.
5. Push a commit - every push triggers a build; the default branch deploys to the Production timeline, other branches get their own branch timelines.
6. Watch builds in the dashboard build log, or trigger manually with Deploy Default Branch (dropdown selects another branch).
7. Optionally consume GitHub repository_dispatch events (deno_deploy.build.enqueued/.cancelled/.failed/.routed) in a GitHub Actions workflow to react to deploy status.
8. Roll back or freeze production independently of git by locking a specific revision as active on the Production timeline.
9. Official docs: https://docs.deno.com/deploy/reference/builds/ ; https://docs.deno.com/deploy/reference/timelines/ ; https://docs.deno.com/deploy/migration_guide/