Visualize possible future moves for any chess position.
active 2025-02-05 → 2025-12-15 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 314 days from 2025-02-05 to 2025-12-15. Pushes: 198 total, peak 19 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 79 total, peak 24 in a day. Comments: 43 total, peak 11 in a day. Stars: 12 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 |
|---|---|---|---|---|
| Phillyclause89 | 319 | 198 | 0 | 43 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#54Phillyclause892025-05-16 22:17Ignored Exception in `CMHMEngine2PoolExecutor` Destructor During Tests Action
- Issue#54Phillyclause892025-05-16 22:17Ignored Exception in `CMHMEngine2PoolExecutor` Destructor During Tests Action
- Issue#54Phillyclause892025-05-16 22:11Ignored Exception in `CMHMEngine2PoolExecutor` Destructor During Tests Action
- Issue#54Phillyclause892025-05-16 22:01Ignored Exception in `CMHMEngine2PoolExecutor` Destructor During Tests Action
- Issue#54Phillyclause892025-05-16 21:54Ignored Exception in `CMHMEngine2PoolExecutor` Destructor During Tests Action
- Issue comment#38Phillyclause892025-05-11 20:20A standalone GUI app is created and supports all core gameplay features of the `PlayCMHMEngine` class.
- Issue comment#38Phillyclause892025-05-11 19:53A standalone GUI app is created and supports all core gameplay features of the `PlayCMHMEngine` class.
- Issue#52Phillyclause892025-05-10 02:29> think of questions someone reading your readme would have, and try to answer them
- Issue comment#5Phillyclause892025-05-10 02:16Update and Expand Documentation
- Issue#5Phillyclause892025-05-10 02:16Update and Expand Documentation
- Issue comment#51Phillyclause892025-05-10 00:23Add Symmetry-Folded Q-Table Keys via Canonical FEN
- Issue#51Phillyclause892025-05-10 00:23Add Symmetry-Folded Q-Table Keys via Canonical FEN
- Issue#51Phillyclause892025-05-09 21:59Add Symmetry-Folded Q-Table Keys via Canonical FEN
- Issue comment#45Phillyclause892025-05-08 03:43Support configuration of engine parameters such as depth and player color in the standalone GUI app.
- Issue#45Phillyclause892025-05-08 03:43Support configuration of engine parameters such as depth and player color in the standalone GUI app.
- Issue comment#49Phillyclause892025-05-08 03:42Bug: Human Player Pawn Promotion Not Functional in `activate_piece` Method
- Issue#49Phillyclause892025-05-08 03:42Bug: Human Player Pawn Promotion Not Functional in `activate_piece` Method
- Issue comment#50Phillyclause892025-05-08 03:41Sweep codebase for unnecessary or incorrect `...[Optional[...]]` type hints
- Issue#50Phillyclause892025-05-08 03:41Sweep codebase for unnecessary or incorrect `...[Optional[...]]` type hints
- Issue#50Phillyclause892025-05-07 17:43Sweep codebase for unnecessary or incorrect `...[Optional[...]]` type hints
- Issue#49Phillyclause892025-05-07 02:35Bug: Human Player Pawn Promotion Not Functional in `activate_piece` Method
- Issue comment#48Phillyclause892025-05-06 21:15Support Game Save/Load System
- Issue comment#45Phillyclause892025-05-06 21:14Support configuration of engine parameters such as depth and player color in the standalone GUI app.
- Issue#48Phillyclause892025-05-06 21:03Support Game Save/Load System
- Issue comment#46Phillyclause892025-05-06 20:58Ensure compatibility with CMHMEngine and CMHMEngine2 for move calculations.
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 12 stars here means stars gained during the window, not the repo's star count.