Skip to content

Command line tool for Deno Deploy

active 2024-07-182026-04-14 (UTC)

Partial coverage15,217 / 18,691 hourly files (81%) · 2 absent upstream · 3,473 failed, retryable2024-06-242026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
170
Pushes
7
Pull requests
16
Issues
22
Stars
28
Forks
10

Activity over time

Daily event counts in the loaded window

Line chart, 636 days from 2024-07-18 to 2026-04-14. Pushes: 7 total, peak 2 in a day. Pull requests: 16 total, peak 2 in a day. Issues: 22 total, peak 2 in a day. Comments: 61 total, peak 17 in a day. Stars: 28 total, peak 2 in a day.

  • Pushes
  • Pull requests
  • Issues
  • Comments
  • Stars

Stars, PRs, issues and forks are under-captured in the later part of this window. GH Archive progressively stopped capturing non-push events during 2026 — −95% or worse by the end of the window. Every series here except Pushes fades for that reason, so a decline above reflects the archive, not this repository. Pushes stay reliable throughout, so read them, and the contributor counts derived from them, as the real signal. Data health has the measurements.

Top contributors

Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity

ContributorContributionsPushesPRsComments
magurotuna5451120
arnauorriols12106
uncenter7015
satyarohith6002
ansipunk5004
justinmchase4002
CLAassistant3003
fro-profesional3001
m0rphed3002
rawkode3002
kt3k3110
hpandelo2001
lumio2001
vicary2002
dgreensp2002
wesbos2002
ngdangtu-vn1001
nicolaefilat1000
katayama80001010
theTechGoose1001

Recent activity

Latest issues, pull requests and releases

  • Issue comment#384deining2026-04-14 06:49
    Fix typos
  • Issue comment#384magurotuna2026-04-14 02:20
    Fix typos
  • Issue#377fro-profesional2025-07-12 17:05
    Avoid saving the config at deno.json
  • Issue comment#376vicary2025-07-11 16:36
    fix(config): prevent repeated inclusion for `exclude`
  • Issue comment#376CLAassistant2025-07-11 16:30
    fix(config): prevent repeated inclusion for `exclude`
  • Issue comment#307vicary2025-07-11 10:34
    `deployctl deploy` when using deno.json config offers to add duplicate node_modules exclude patterns
  • Issue#372magurotuna2025-07-08 07:34
    p
  • Issue#374kindkitchen2025-06-18 19:05
    Possibility to deploy from tag instead of branch
  • Issue comment#373lumio2025-06-01 11:18
    Allow setting custom --env vars through GH action denoland/deployctl@v1
  • Issue#373lumio2025-06-01 11:18
    Allow setting custom --env vars through GH action denoland/deployctl@v1
  • Issue#369JounQin2025-04-13 18:28
    `nodeModulesDir: manual` takes no effect
  • Issue comment#311zing-rsa2025-04-12 16:39
    [Bug]: deployctl deploy executes entrypoint before setting --env vars
  • Issue comment#359uncenter2025-04-08 22:34
    feat: use @deno/cache-dir to resolve deno dir
  • Pull request#358uncenter2025-04-08 22:33
  • Pull request#367kt3k2025-03-18 04:55
  • Issue comment#360hpandelo2025-03-12 03:41
    🚀 Feature Request: Allow specifying Deno version in `deployctl`
  • Issue#366hpandelo2025-03-12 03:23
    401 Unauthorized when using a private package (on github registry)
  • Issue#364justinmchase2025-03-01 17:36
    Use ohid when deploying from the cli in an action
  • Issue comment#298justinmchase2025-03-01 16:34
    deployctl is not able to read env secret in GitHub Action
  • Issue#363justinmchase2025-03-01 15:54
    The deploy action isn't resolving the entrpoint path correctly
  • Issue comment#302justinmchase2025-03-01 15:48
    Support GitHub Deployments from deployctl cli
  • Issue#362frou2025-02-22 10:58
    Live logs (`deployctl logs`) may not show the actual latest deployment
  • Issue#324magurotuna2025-02-14 06:19
    The deployment failed: Relative import path, but import path was specified in deno.json imports section
  • Issue#324magurotuna2025-02-14 06:19
    The deployment failed: Relative import path, but import path was specified in deno.json imports section
  • Pull request#326magurotuna2025-02-14 06:19

Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 28 stars here means stars gained during the window, not the repo's star count.