Supervisor trees for Go.
active 2023-08-18 → 2026-05-22 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 1009 days from 2023-08-18 to 2026-05-22. Pushes: 9 total, peak 5 in a day. Pull requests: 4 total, peak 1 in a day. Issues: 12 total, peak 2 in a day. Comments: 16 total, peak 2 in a day. Stars: 170 total, peak 3 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| thejerf | 24 | 9 | 1 | 8 |
| jalaziz | 6 | 0 | 1 | 4 |
| iwittkau | 2 | 0 | 1 | 1 |
| flowchartsman | 2 | 0 | 0 | 1 |
| quad | 1 | 0 | 0 | 0 |
| szabba | 1 | 0 | 0 | 1 |
| marco-m | 1 | 0 | 0 | 0 |
| yurivish | 1 | 0 | 1 | 0 |
| vtolstov | 1 | 0 | 0 | 0 |
| erincandescent | 1 | 0 | 0 | 0 |
| bn-jbowers | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#78jalaziz2026-05-21 05:15Add events for service start and stop
- Issue comment#79szabba2025-08-14 17:39Update README.md to link to the v4 docs
- Pull request#79yurivish2025-08-13 15:32
- Issue comment#78jalaziz2025-02-18 02:38Add events for service start and stop
- Pull request#78jalaziz2025-02-18 02:37
- Issue comment#76thejerf2024-12-07 19:03Lack of observability during successful operation
- Issue#76thejerf2024-12-07 19:03Lack of observability during successful operation
- Issue comment#76jalaziz2024-12-03 06:56Lack of observability during successful operation
- Issue comment#76thejerf2024-11-29 16:39Lack of observability during successful operation
- Issue#76thejerf2024-11-29 16:39Lack of observability during successful operation
- Issue comment#77thejerf2024-11-29 16:37Leakage of context errors can tear down a service
- Issue#77thejerf2024-11-29 16:37Leakage of context errors can tear down a service
- Issue comment#77thejerf2024-11-06 20:49Leakage of context errors can tear down a service
- Issue#77erincandescent2024-11-06 10:10Leakage of context errors can tear down a service
- Issue comment#76jalaziz2024-04-09 08:26Lack of observability during successful operation
- Issue#76jalaziz2024-04-09 08:21Lack of observability during successful operation
- Issue#75quad2024-03-28 05:08Add a note that the `one_for_one` restart strategy is used
- Issue comment#72iwittkau2024-03-14 14:43EventStopTimeout: use reflection for type printing
- Issue comment#74thejerf2024-03-10 23:30scale one service to two or more instances
- Issue#74thejerf2024-03-10 23:30scale one service to two or more instances
- Issue#74vtolstov2024-03-10 20:36scale one service to two or more instances
- Issue#73thejerf2024-03-08 16:41EventStopTimeout exposes all struct field values.
- Issue comment#72thejerf2024-03-08 16:40EventStopTimeout: use reflection for type printing
- Pull request#72thejerf2024-03-08 16:40
- Issue comment#73bn-jbowers2024-03-08 16:36EventStopTimeout exposes all struct field values.
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 170 stars here means stars gained during the window, not the repo's star count.