active 2025-05-18 → 2025-11-20 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 187 days from 2025-05-18 to 2025-11-20. Pushes: 69 total, peak 23 in a day. Pull requests: 85 total, peak 34 in a day. Issues: 58 total, peak 38 in a day. Comments: 44 total, peak 23 in a day. Stars: 1 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
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| Copilot | 123 | 34 | 27 | 39 |
| onnwee | 99 | 29 | 14 | 2 |
| github-actions[bot] | 47 | 0 | 38 | 0 |
| PatrickFanella | 20 | 6 | 2 | 0 |
| dependabot[bot] | 4 | 0 | 4 | 0 |
| gitguardian[bot] | 2 | 0 | 0 | 2 |
| github-advanced-security[bot] | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Pull request#61dependabot[bot]2025-11-20 02:57
- Pull request#61github-actions[bot]2025-11-20 02:57
- Pull request#60dependabot[bot]2025-10-21 03:59
- Pull request#60dependabot[bot]2025-10-21 03:59
- Issue#59github-actions[bot]2025-10-18 14:24Router and server setup is repeated across many tests. Consider extracting a small helper (e.g., newTestRouterWithProjectRoutes or a generic newTestServerAndRouter) to reduce duplication and make future test additions simpler.
- Pull request#56github-actions[bot]2025-10-18 01:05
- Pull request#56github-actions[bot]2025-10-18 01:05
- Issue#55onnwee2025-10-18 01:05The script lacks proper error handling for the migration command. If 'migrate up' fails, the script will exit but won't provide clear feedback about what went wrong. Consider adding explicit error handling after the migrate command.
- Pull request#58Copilot2025-10-18 00:56
- Issue#13onnwee2025-10-18 00:56[Testing] Backend handlers unit tests
- Pull request#58Copilot2025-10-18 00:56
- Pull request#58Copilot2025-10-18 00:56
- Issue#19onnwee2025-10-18 00:53[Frontend] Route-level ErrorBoundaries + skeletons
- Pull request#57Copilot2025-10-18 00:53
- Pull request#57Copilot2025-10-18 00:53
- Pull request#57Copilot2025-10-18 00:53
- Issue comment#56gitguardian[bot]2025-10-18 00:52[WIP] Add error handling for migration command
- Issue#12github-actions[bot]2025-10-18 00:51[Backend] Database migrations via goose or golang-migrate
- Pull request#50github-actions[bot]2025-10-18 00:51
- Issue#12onnwee2025-10-18 00:51[Backend] Database migrations via goose or golang-migrate
- Pull request#56Copilot2025-10-18 00:47
- Issue#55github-actions[bot]2025-10-18 00:47The script lacks proper error handling for the migration command. If 'migrate up' fails, the script will exit but won't provide clear feedback about what went wrong. Consider adding explicit error handling after the migrate command.
- Pull request#53github-actions[bot]2025-10-18 00:16
- Pull request#53github-actions[bot]2025-10-18 00:16
- Pull request#53onnwee2025-10-18 00:03
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 1 stars here means stars gained during the window, not the repo's star count.