active 2025-04-03 → 2026-05-16 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 409 days from 2025-04-03 to 2026-05-16. Pushes: 51 total, peak 6 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 5 total, peak 1 in a day. Comments: 17 total, peak 4 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 |
|---|---|---|---|---|
| nmunro | 58 | 49 | 0 | 8 |
| truedat101 | 11 | 0 | 0 | 8 |
| EverChange000 | 1 | 0 | 0 | 0 |
| StellarSyzygy | 1 | 0 | 0 | 1 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#10StellarSyzygy2026-05-16 04:09Tutorial 6 Postgresql - Name service error in "getaddrinfo"
- Issue#3nmunro2026-05-15 23:24database name path with ~ isn't resolved on Mac OS X / Week 6
- Issue comment#9nmunro2026-01-25 11:38week 9 : question about dotenv configuration and ningle-auth/migrations.lisp
- Issue comment#8truedat1012026-01-25 01:21Week 9: sqlx conflict with ningl-auth in ningle-auth main.lisp
- Issue#6truedat1012026-01-17 09:41Week 8: typo in ningle-auth section related to template directory path
- Issue comment#6nmunro2025-12-20 22:52Week 8: typo in ningle-auth section related to template directory path
- Issue comment#5truedat1012025-12-20 22:25Week 7 : incomplete .env setup will cause config.lisp to fail in compilation
- Issue comment#5nmunro2025-12-20 10:28Week 7 : incomplete .env setup will cause config.lisp to fail in compilation
- Issue comment#5truedat1012025-12-20 10:03Week 7 : incomplete .env setup will cause config.lisp to fail in compilation
- Issue#6truedat1012025-12-20 10:03Week 8: typo in ningle-auth section related to template directory path
- Issue comment#5truedat1012025-12-05 19:40Week 7 : incomplete .env setup will cause config.lisp to fail in compilation
- Issue comment#5nmunro2025-12-05 14:41Week 7 : incomplete .env setup will cause config.lisp to fail in compilation
- Issue comment#4nmunro2025-12-05 10:03envy-ningle typo in article for week7: references extract-mito-config , but this method no longer exists, renamed to extract-middleware-config
- Issue comment#4truedat1012025-12-05 09:00envy-ningle typo in article for week7: references extract-mito-config , but this method no longer exists, renamed to extract-middleware-config
- Issue comment#4truedat1012025-12-04 23:46envy-ningle typo in article for week7: references extract-mito-config , but this method no longer exists, renamed to extract-middleware-config
- Issue comment#4truedat1012025-12-04 23:46envy-ningle typo in article for week7: references extract-mito-config , but this method no longer exists, renamed to extract-middleware-config
- Issue comment#4truedat1012025-12-04 21:43envy-ningle typo in article for week7: references extract-mito-config , but this method no longer exists, renamed to extract-middleware-config
- Issue comment#4nmunro2025-12-04 21:33envy-ningle typo in article for week7: references extract-mito-config , but this method no longer exists, renamed to extract-middleware-config
- Issue comment#2nmunro2025-11-17 10:20ingle should be explained when it is introduced
- Issue comment#2nmunro2025-11-16 19:48ingle should be explained when it is introduced
- Issue#2truedat1012025-11-16 00:20ingle should be explained when it is introduced
- Issue#1EverChange0002025-11-08 20:12Errors in https://nmunro.github.io/2025/01/30/ningle-3.html
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.