A cli for loops
active 2026-07-03 → 2026-07-27 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 25 days from 2026-07-03 to 2026-07-27. Pushes: 41 total, peak 9 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 5 total, peak 2 in a day. Comments: 0 total, peak 0 in a day. Stars: 0 total, peak 0 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 |
|---|---|---|---|---|
| CKGrafico | 46 | 41 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue#41CKGrafico2026-07-09 09:33As a user, I want to connect a GitHub repository to my project so that future features can leverage repository metadata and remote context
- Issue#33CKGrafico2026-07-08 15:51User Story: Manual-Only Loops — zero/manual interval loops that only run on explicit trigger
- Issue#34CKGrafico2026-07-08 15:33As a loop creator, I want to pass an initial context object to a chained task so that my parameters propagate through the entire onSuccess/onFailure chain
- Issue#35CKGrafico2026-07-07 19:33'Refactor: Kill board/ dead code and extract shared/ui layer'
- Issue#21CKGrafico2026-07-04 22:57As a user, I want a polished loop create/edit form with task selection, inline command editing, smart defaults, and field validation — so I can efficiently configure loops without confusion or data-entry errors
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.