Skip to content

active 2023-10-122025-08-06 (UTC)

Complete coverage26,716 / 26,716 hourly files (100%) · 2 absent upstream2023-08-152026-09-01 (UTC)
Events
387
Pushes
361
Pull requests
0
Issues
4
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 665 days from 2023-10-12 to 2025-08-06. Pushes: 361 total, peak 26 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 4 total, peak 1 in a day. Comments: 22 total, peak 15 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
user1095108365350012
user706110010

Recent activity

Latest issues, pull requests and releases

  • Issue comment#5user10951082023-10-16 06:35
    stack-allocated buffer (size specified during runtime, and then fixed)
  • Issue#5user10951082023-10-16 06:35
    stack-allocated buffer (size specified during runtime, and then fixed)
  • Issue comment#6user10951082023-10-14 06:13
    push_front semantics
  • Issue#6user10951082023-10-14 06:13
    push_front semantics
  • Issue#7user10951082023-10-13 07:51
    Bug in operator=
  • Issue comment#5user10951082023-10-13 02:28
    stack-allocated buffer (size specified during runtime, and then fixed)
  • Issue comment#7user10951082023-10-13 02:27
    Bug in operator=
  • Issue comment#6user10951082023-10-13 02:24
    push_front semantics
  • Issue comment#5user7062023-10-12 21:51
    stack-allocated buffer (size specified during runtime, and then fixed)
  • Issue comment#5user7062023-10-12 18:29
    stack-allocated buffer (size specified during runtime, and then fixed)
  • Issue comment#7user7062023-10-12 17:24
    Bug in operator=
  • Issue comment#7user7062023-10-12 17:21
    Bug in operator=
  • Issue comment#5user7062023-10-12 16:26
    stack-allocated buffer (size specified during runtime, and then fixed)
  • Issue comment#5user10951082023-10-12 15:55
    stack-allocated buffer (size specified during runtime, and then fixed)
  • Issue comment#6user7062023-10-12 14:56
    push_front semantics
  • Issue comment#5user10951082023-10-12 14:25
    stack-allocated buffer
  • Issue comment#6user10951082023-10-12 14:21
    push_front semantics
  • Issue comment#5user7062023-10-12 13:27
    stack-allocated buffer
  • Issue comment#5user7062023-10-12 12:32
    stack-allocated buffer
  • Issue comment#5user7062023-10-12 12:17
    stack-allocated buffer
  • Issue comment#5user10951082023-10-12 09:58
    stack-allocated buffer
  • Issue comment#5user10951082023-10-12 09:41
    stack-allocated buffer
  • Issue#5user7062023-10-12 08:12
    stack-allocated buffer

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.