Skip to content

active 2025-03-302026-04-11 (UTC)

Partial coverage11,343 / 12,181 hourly files (93%) · 2 absent upstream · 835 failed, retryable2025-03-212026-08-10 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
33
Pushes
9
Pull requests
0
Issues
5
Stars
12
Forks
4

Activity over time

Daily event counts in the loaded window

Line chart, 378 days from 2025-03-30 to 2026-04-11. Pushes: 9 total, peak 2 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 5 total, peak 1 in a day. Comments: 3 total, peak 1 in a day. Stars: 12 total, peak 1 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
ionic-bond8601
shmilyhua5002
bay1ts1000
github-actions[bot]1100

Recent activity

Latest issues, pull requests and releases

  • Issue#15shmilyhua2026-01-18 14:52
    Further API changes (error: 400 {"errors":[{"message":"The following features cannot be null: responsive_web_profile_redirect_enabled")
  • Issue comment#15shmilyhua2025-11-07 18:25
    Further API changes (error: 400 {"errors":[{"message":"The following features cannot be null: responsive_web_profile_redirect_enabled")
  • Issue#13shmilyhua2025-09-30 13:06
    If the monitored user post a tweet quickly after (or before?) deleting some tweets, it wont be crawled.
  • Issue comment#13shmilyhua2025-08-18 07:23
    If the monitored user post a tweet quickly after (or before?) deleting some tweets, it wont be crawled.
  • Issue comment#13ionic-bond2025-08-17 15:39
    If the monitored user post a tweet quickly after (or before?) deleting some tweets, it wont be crawled.
  • Issue#13shmilyhua2025-08-17 12:12
    If the monitored user post a tweet quickly after (or before?) deleting some tweets, it wont be crawled.
  • Issue#11ionic-bond2025-07-27 09:02
    If the tweet is too long, it won't be completely forwarded to the Telegram channel.
  • Issue#10bay1ts2025-04-24 03:16
    login failed

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