Skip to content

active 2025-09-242025-11-06 (UTC)

Partial coverage12,420 / 14,129 hourly files (88%) · 2 absent upstream · 1,703 failed, retryable2024-12-302026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
53
Pushes
14
Pull requests
0
Issues
19
Stars
0
Forks
0

Activity over time

Daily event counts in the loaded window

Line chart, 44 days from 2025-09-24 to 2025-11-06. Pushes: 14 total, peak 4 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 19 total, peak 6 in a day. Comments: 8 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
github-actions[bot]30408
DevMello111000

Recent activity

Latest issues, pull requests and releases

  • Issue#11github-actions[bot]2025-11-06 21:34
    Implement MeepMeep auto path
  • Issue#10DevMello2025-11-06 21:31
    Create base auto class
  • Releasegithub-actions[bot]2025-11-06 21:25
    Release 14
  • Issue#24github-actions[bot]2025-11-06 21:24
    add two distance sensors to detect artifacts on each side of the intake
  • Issue comment#24github-actions[bot]2025-11-06 21:24
    add two distance sensors to detect artifacts on each side of the intake
  • Issue comment#9github-actions[bot]2025-11-06 21:24
    Implement MeepMeep auto path
  • Issue comment#20github-actions[bot]2025-11-06 21:24
    (Far Blue) Fix Auto Path to shoot from launch zone
  • Issue comment#19github-actions[bot]2025-11-06 21:24
    (Close Red) Fix Auto Path to shoot from launch zone
  • Issue#18github-actions[bot]2025-11-06 21:24
    (Close Blue) Fix Auto Path to shoot from launch zone
  • Issue comment#18github-actions[bot]2025-11-06 21:24
    (Close Blue) Fix Auto Path to shoot from launch zone
  • Releasegithub-actions[bot]2025-11-06 21:22
    Release 13
  • Issue comment#17github-actions[bot]2025-11-06 20:52
    Add a check to see if the robot is in a valid launch zone
  • Issue#23github-actions[bot]2025-10-05 01:01
    Store both of these GOAL_POSES in a List and select based on team color
  • Issue comment#22github-actions[bot]2025-10-05 01:01
    Test TODO workflow and check if it works
  • Issue#22github-actions[bot]2025-10-05 01:01
    Test TODO workflow and check if it works
  • Releasegithub-actions[bot]2025-10-01 16:00
    Release 8
  • Issue#19github-actions[bot]2025-10-01 15:59
    (Close Red) Fix Auto Path to shoot from launch zone
  • Releasegithub-actions[bot]2025-10-01 15:54
    Release 7
  • Issue#17github-actions[bot]2025-10-01 15:53
    Add a check to see if the robot is in a valid launch zone
  • Releasegithub-actions[bot]2025-10-01 04:53
    Release 5
  • Releasegithub-actions[bot]2025-09-30 18:57
    Release 4
  • Issue#15github-actions[bot]2025-09-30 18:56
    make sure your config has a Pinpoint device with this
  • Releasegithub-actions[bot]2025-09-30 18:40
    Release 2
  • Issue comment#4github-actions[bot]2025-09-29 00:04
    Complete Far Red autonomous routine
  • Issue#4github-actions[bot]2025-09-29 00:04
    Complete Far Red autonomous routine

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.