active 2026-02-10 → 2026-03-02 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 21 days from 2026-02-10 to 2026-03-02. Pushes: 8 total, peak 3 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 20 total, peak 6 in a day. Comments: 9 total, peak 8 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
Recent activity
Latest issues, pull requests and releases
- Issue#27mofeejegi2026-03-02 21:18Unit test writing guide: explicitly gate marker removal at Phase 2 checkpoint
- Issue comment#10wtmoose2026-02-28 20:13Code organization policy should require alerting human on codebase conflicts
- Issue#10wtmoose2026-02-28 20:13Code organization policy should require alerting human on codebase conflicts
- Issue#17wtmoose2026-02-28 20:06Research prior art in forums and related projects before proposing fixes
- Issue#18wtmoose2026-02-28 20:06Explicit consent gate before implementing fixes
- Issue comment#18wtmoose2026-02-28 20:06Explicit consent gate before implementing fixes
- Issue comment#17wtmoose2026-02-28 20:06Research prior art in forums and related projects before proposing fixes
- Issue#16wtmoose2026-02-28 20:06Propose reproducing bugs in unit tests as a discriminating experiment
- Issue comment#13wtmoose2026-02-28 20:06Global 🟡 lifecycle rule to prevent premature resolution
- Issue comment#11wtmoose2026-02-28 20:06Retro process reflection should include evaluation criteria for suggestions
- Issue#5wtmoose2026-02-28 20:06Debugging guide should define "code bisection" concretely
- Issue#7wtmoose2026-02-28 20:06Process ticket guide should include explicit label options
- Issue comment#7wtmoose2026-02-28 20:06Process ticket guide should include explicit label options
- Issue comment#4wtmoose2026-02-28 20:06Process ticket guide should include explicit label options
- Issue comment#3wtmoose2026-02-28 20:06Debugging guide should distinguish "test hypothesis" from "apply fix"
- Issue#24wtmoose2026-02-27 19:33Reinforce existing-infrastructure search before creating new test doubles
- Issue#24wtmoose2026-02-27 19:33Reinforce existing-infrastructure search before creating new test doubles
- Issue#23wtmoose2026-02-27 19:33Add anti-pattern for skipping tests that need production code changes
- Issue#22wtmoose2026-02-27 19:33Add test double naming convention to infrastructure guide
- Issue#22wtmoose2026-02-27 19:33Add test double naming convention to infrastructure guide
- Issue#20wtmoose2026-02-25 18:08Hard prohibition on destructive git operations without explicit human approval
- Issue#17wtmoose2026-02-24 22:53Research prior art in forums and related projects before proposing fixes
- Issue#8wtmoose2026-02-22 22:02Test
- Issue comment#8wtmoose2026-02-22 22:02Test
- Issue#7wtmoose2026-02-22 22:02Process ticket guide should include explicit label options
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.