Unittest wrapper focussed on DB integrity tests. Is your tool hard to debug? is it easier if you check it at the DB level? this module is for you
active 2023-09-19 → 2023-09-20 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 2 days from 2023-09-19 to 2023-09-20. Pushes: 27 total, peak 16 in a day. Pull requests: 4 total, peak 3 in a day. Issues: 0 total, peak 0 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
Top contributors
Pushes, PRs, issues, reviews and comments — stars and forks excluded, so this is contribution rather than popularity
| Contributor | Contributions | Pushes | PRs | Comments |
|---|---|---|---|---|
| cortze | 31 | 27 | 4 | 0 |
Recent activity
Latest issues, pull requests and releases
- Releasecortze2023-09-20 16:19v0.1.0 - PRanger
- Pull request#2cortze2023-09-20 16:04
- Pull request#2cortze2023-09-20 15:59
- Pull request#1cortze2023-09-20 10:12
- Pull request#1cortze2023-09-19 18:11
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.