Skip to content

brotherlogic/devcontainer-manager

View on GitHub ↗Related repositories →

A project to keep devcontainers up to date

active 2026-03-152026-08-19 (UTC)

Complete coverage26,700 / 26,700 hourly files (100%) · 2 absent upstream2023-08-152026-08-31 (UTC)
Events
446
Pushes
136
Pull requests
29
Issues
48
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 158 days from 2026-03-15 to 2026-08-19. Pushes: 136 total, peak 7 in a day. Pull requests: 29 total, peak 4 in a day. Issues: 48 total, peak 9 in a day. Comments: 35 total, peak 5 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
brotherlogic2081172816
github-actions[bot]270019
brotherlogic-automation251910

Recent activity

Latest issues, pull requests and releases

  • Issue#397brotherlogic-automation2026-08-19 00:40
    [Breakdown] Perform periodic disk cleaning to prevent container startup failures
  • Issue#376brotherlogic2026-08-12 00:26
    [Bug] Add mutex locking around devpod CLI invocations to prevent config race conditions
  • Issue#376brotherlogic2026-08-11 22:45
    [Bug] Add mutex locking around devpod CLI invocations to prevent config race conditions
  • Issue#373brotherlogic2026-08-11 21:50
    Issue Container Startup Failed
  • Issue#365brotherlogic2026-08-09 01:28
    [Sub-Issue] Add unit tests for HARNESS_PI and HARNESS_UNSPECIFIED handling
  • Issue#363brotherlogic2026-08-09 00:36
    [Sub-Issue] Implement strict failure handling for HARNESS_PI in injectStartupCommand
  • Issue#363brotherlogic2026-08-09 00:19
    [Sub-Issue] Implement strict failure handling for HARNESS_PI in injectStartupCommand
  • Issue#365brotherlogic2026-08-09 00:19
    [Sub-Issue] Add unit tests for HARNESS_PI and HARNESS_UNSPECIFIED handling
  • Issue#359brotherlogic-automation2026-08-08 23:39
    Requirements gathering for Pi harness execution and failure fallback handling (parent #357)
  • Issue#286brotherlogic-automation2026-07-23 23:10
    [Sub-Issue] Implement createIssueWithDeduplication helper function
  • Issue#264brotherlogic-automation2026-07-23 04:25
    [Breakdown] Add a CUI interface for testing the manager
  • Pull request#221brotherlogic-automation2026-07-04 22:47
  • Issue#194brotherlogic2026-06-24 03:08
    Requirements Gathering: Container Startup Failed (from #193)
  • Issue#179brotherlogic2026-06-24 02:58
    Move this to run in Kubernetes
  • Issue#179brotherlogic2026-06-24 02:22
    Move this to run in Kubernetes
  • Issue#194brotherlogic2026-06-24 02:21
    Requirements Gathering: Container Startup Failed (from #193)
  • Issue#194brotherlogic2026-06-24 02:21
    Requirements Gathering: Container Startup Failed (from #193)
  • Issue#192brotherlogic2026-06-24 00:41
    Use the project to track token usage
  • Issue#192brotherlogic2026-06-23 22:38
    Use the project to track token usage
  • Issue#192brotherlogic2026-06-23 21:54
    Use the project to track token usage
  • Issue#179brotherlogic2026-06-23 21:48
    Move this to run in Kubernetes
  • Issue#192brotherlogic2026-06-23 20:42
    Use the project to track token usage
  • Issue#192brotherlogic2026-06-23 19:58
    Use the project to track token usage
  • Issue#194brotherlogic2026-06-23 16:22
    Requirements Gathering: Container Startup Failed (from #193)
  • Issue#194brotherlogic2026-06-23 10:32
    Requirements Gathering: Container Startup Failed (from #193)

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.