Skip to content

Local first, durable action runner

active 2026-03-062026-03-30 (UTC)

Partial coverage20,529 / 26,285 hourly files (78%) · 2 absent upstream · 5,753 failed, retryable2023-08-152026-08-14 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
59
Pushes
27
Pull requests
0
Issues
25
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 25 days from 2026-03-06 to 2026-03-30. Pushes: 27 total, peak 6 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 25 total, peak 20 in a day. Comments: 6 total, peak 6 in a day. Stars: 0 total, peak 0 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
jorgt582706

Recent activity

Latest issues, pull requests and releases

  • Issue#13jorgt2026-03-14 22:04
    Backfill active singleton metadata when migrating existing SQLite stores
  • Issue#8jorgt2026-03-14 22:04
    More recognisable statuses in UI (running, idle, deferred, error, completed)
  • Issue#1jorgt2026-03-14 22:04
    Add retention option to auto-prune old runs
  • Issue#20jorgt2026-03-14 04:45
    Fence stale handlers after lease loss and heartbeat failure
  • Issue#22jorgt2026-03-14 04:45
    Backfill emission reservations when migrating existing SQLite stores
  • Issue#19jorgt2026-03-14 04:45
    Secure the dev server control plane (wide-open CORS + unauthenticated mutations)
  • Issue#28jorgt2026-03-14 04:45
    Retention can break emitAndWait by pruning roots before descendant chains finish
  • Issue#27jorgt2026-03-14 04:45
    Add a repair path for effects stuck in started state
  • Issue#23jorgt2026-03-14 04:45
    Backfill active singleton metadata when migrating existing SQLite stores
  • Issue#24jorgt2026-03-14 04:45
    Do not reclaim persisted work before handlers have finished registering
  • Issue#21jorgt2026-03-14 04:45
    Hard stop leaves aborted runs stuck in running state
  • Issue#25jorgt2026-03-14 04:45
    Child runs inherit non-durable local context mutations
  • Issue#26jorgt2026-03-14 04:45
    Surface chained-event admission failures instead of silently truncating the chain
  • Issue comment#19jorgt2026-03-14 04:45
    Secure the dev server control plane (wide-open CORS + unauthenticated mutations)
  • Issue comment#27jorgt2026-03-14 04:45
    Add a repair path for effects stuck in started state
  • Issue comment#23jorgt2026-03-14 04:45
    Backfill active singleton metadata when migrating existing SQLite stores
  • Issue comment#25jorgt2026-03-14 04:45
    Child runs inherit non-durable local context mutations
  • Issue comment#28jorgt2026-03-14 04:45
    Retention can break emitAndWait by pruning roots before descendant chains finish
  • Issue comment#24jorgt2026-03-14 04:45
    Do not reclaim persisted work before handlers have finished registering
  • Issue#28jorgt2026-03-14 04:18
    Retention can break emitAndWait by pruning roots before descendant chains finish
  • Issue#24jorgt2026-03-14 04:18
    Do not reclaim persisted work before handlers have finished registering
  • Issue#22jorgt2026-03-14 04:18
    Backfill emission reservations when migrating existing SQLite stores
  • Issue#20jorgt2026-03-14 04:18
    Fence stale handlers after lease loss and heartbeat failure
  • Issue#18jorgt2026-03-14 04:15
    Retention can break emitAndWait by pruning roots before descendant chains finish
  • Issue#11jorgt2026-03-14 04:15
    Hard stop leaves aborted runs stuck in running state

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