This is a REST API to manage technical incidents
active 2025-02-16 → 2025-06-16 (UTC)
Partial coverage12,307 / 14,012 hourly files (88%) · 2 absent upstream · 1,699 failed, retryable2025-01-04 → 2026-08-11 (UTC)— sampled evenly across the window, so rankings and trends hold; absolute counts scale up.
Events
20
Pushes
5
Pull requests
7
Issues
0
Stars
0
Forks
0
Activity over time
Daily event counts in the loaded window
Line chart, 121 days from 2025-02-16 to 2025-06-16. Pushes: 5 total, peak 2 in a day. Pull requests: 7 total, peak 2 in a day. Issues: 0 total, peak 0 in a day. Comments: 5 total, peak 2 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 |
|---|---|---|---|---|
| diegoTech14 | 12 | 5 | 7 | 0 |
| openzeppelin-code[bot] | 5 | 0 | 0 | 5 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#9openzeppelin-code[bot]2025-06-16 23:40feat: added new queries for incidents
- Pull request#9diegoTech142025-06-16 23:39
- Pull request#8diegoTech142025-06-07 02:30
- Issue comment#8openzeppelin-code[bot]2025-05-09 05:30feat: added hash functionality and JSON middleware
- Pull request#8diegoTech142025-05-09 05:29
- Issue comment#7openzeppelin-code[bot]2025-04-12 04:49feat: dockerizing app and database
- Pull request#7diegoTech142025-04-12 04:49
- Issue comment#7openzeppelin-code[bot]2025-04-12 02:12feat: dockerizing app and database
- Pull request#7diegoTech142025-04-12 02:10
- Pull request#6diegoTech142025-03-19 04:23
- Issue comment#6openzeppelin-code[bot]2025-02-16 22:26Feat: added the repository pattern for users and incidents entities
- Pull request#6diegoTech142025-02-16 22:25
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.