Skip to content

New Deno Deploy docs: production-branch location, disabling preview deploys, and CI --token auth are missing/outdated #3280

Description

@JoshuaVSherman

Setting up a new app on the new Deno Deploy (console.deno.com) — a scheduled Deno.cron service deployed from CI — I hit several documentation gaps where the docs were vague or didn't match the current dashboard. Sharing as constructive feedback:

  1. Production branch location. Docs imply the production branch is set under a "Git" tab in app Settings, but in the current UI the branch selector is on the app Settings page directly — there is no "Git" tab. The pointer sent me hunting.

  2. Entrypoint field is hidden. During app creation the required Entry point field is collapsed behind an "Edit app configuration" button. This isn't documented and is easy to miss that the field exists.

  3. No documented way to disable preview/branch deployments. With the GitHub integration, every branch builds (production branch → production, others → preview) and each PR gets a deploy/<org>/<app> status check. For a service that should deploy only from main, there's no documented setting to turn off preview/branch deploys or the PR status check — only per-commit [skip deploy]. Please document whether this is configurable.

  4. CI/CD token auth is undocumented. The CLI reference states "the CLI will prompt for authentication" and doesn't mention non-interactive auth. I only discovered deno deploy --token <token> by running deno deploy --help. Please document --token (and any env-var equivalent) for CI/CD use.

  5. General: the new-platform UI docs lag the actual dashboard — exact field labels and a screenshot-level "create app from GitHub" walkthrough would help a lot.

Versions: Deno 2.8.2, @deno/deploy 0.0.99, console.deno.com (new platform), June 2026.

Suggestion: a current "Deploy from GitHub via the dashboard" walkthrough with real labels, the production-branch location, a preview-deploy toggle (or how to deploy only the production branch), and a CI/CD section covering --token.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions