Created a codebase exercise to help my team understand how to navigate a codebase to find issues.
active 2023-11-21 → 2023-11-21 (UTC)
Partial coverage22,127 / 26,309 hourly files (84%) · 2 absent upstream · 4,181 failed, retryable2023-08-15 → 2026-08-15 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
8
Pushes
1
Pull requests
0
Issues
2
Stars
0
Forks
2
Activity over time
Daily event counts in the loaded window
Line chart, 1 days from 2023-11-21 to 2023-11-21. Pushes: 1 total, peak 1 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 2 total, peak 2 in a day. Comments: 1 total, peak 1 in a day. Stars: 0 total, peak 0 in a day.
- Pushes
- Pull requests
- Issues
- Comments
- Stars
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
Recent activity
Latest issues, pull requests and releases
- Issue comment#2kennykguo2023-11-21 23:14For some reason, the program is giving me the wrong numbers
- Issue#2dev-jesse2023-11-21 22:58For some reason, the program is giving me the wrong numbers
- Issue#1dev-jesse2023-11-21 22:57Change the readme to reflect what the program really does
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.