Repo to test HitHub jira syncing
active 2024-09-29 → 2026-01-15 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 474 days from 2024-09-29 to 2026-01-15. Pushes: 0 total, peak 0 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 105 total, peak 20 in a day. Comments: 40 total, peak 8 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 |
|---|---|---|---|---|
| textagroup | 112 | 0 | 0 | 21 |
| mbesina-innocraft | 27 | 0 | 0 | 16 |
| des-innocraft | 4 | 0 | 0 | 3 |
| glitchhunter66 | 2 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#47textagroup2026-01-15 00:52Testing if multiple updates are processed correctly Part 3
- Issue comment#47textagroup2026-01-15 00:47Testing if multiple updates are processed correctly Part 3
- Issue comment#46textagroup2026-01-15 00:47Testing if multiple updates are processed correctly Part 2
- Issue comment#45textagroup2026-01-15 00:47Testing if multiple updates are processed correctly Part 1
- Issue comment#47textagroup2026-01-15 00:45Testing if multiple updates are processed correctly Part 3
- Issue comment#46textagroup2026-01-15 00:42Testing if multiple updates are processed correctly Part 2
- Issue#47textagroup2026-01-15 00:41Testing if multiple updates are processed correctly Part 3
- Issue comment#45textagroup2026-01-15 00:38Testing if multiple updates are processed correctly Part 1
- Issue#46textagroup2026-01-15 00:21Testing if multiple updates are processed correctly Part 2
- Issue#45textagroup2026-01-15 00:21Testing if multiple updates are processed correctly Part 1
- Issue comment#44textagroup2026-01-15 00:01Check if multiple closing and opening caused issues for syncing
- Issue#44textagroup2026-01-15 00:00Check if multiple closing and opening caused issues for syncing
- Issue comment#43textagroup2026-01-14 22:21Github to Jira, move to Cloud, move jira ticket to Done and comment on Github
- Issue comment#43textagroup2026-01-14 22:17Github to Jira, move to Cloud, move jira ticket to Done and comment on Github
- Issue comment#43textagroup2026-01-14 22:05Github to Jira, move to Cloud, move jira ticket to Done and comment on Github
- Issue comment#43mbesina-innocraft2026-01-12 20:26Github to Jira, move to Cloud, move jira ticket to Done and comment on Github
- Issue comment#42textagroup2026-01-12 19:46Create E2E test, move ticket to In Progress, add details from Github
- Issue comment#41mbesina-innocraft2026-01-12 03:52E2E - Creating GitHub issue, moving ticket to CLOUD and moving status to CLOSED.
- Issue comment#42mbesina-innocraft2026-01-12 03:45Create E2E test, move ticket to In Progress, add details from Github
- Issue comment#41mbesina-innocraft2026-01-12 03:34E2E - Creating GitHub issue, moving ticket to CLOUD and moving status to CLOSED.
- Issue comment#42mbesina-innocraft2026-01-12 03:34Create E2E test, move ticket to In Progress, add details from Github
- Issue comment#42mbesina-innocraft2026-01-12 03:02Create E2E test, move ticket to In Progress, add details from Github
- Issue#42mbesina-innocraft2026-01-12 02:57Create E2E test, move ticket to In Progress, add details from Github
- Issue#39mbesina-innocraft2026-01-11 23:21E2E - Creating GitHub issue, moving ticket to PG and closing GitHub issue.
- Issue comment#39mbesina-innocraft2026-01-11 23:16E2E - Creating GitHub issue, moving ticket to PG and closing GitHub issue.
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.