Fully automatic on x11 and wayland
active 2024-05-31 → 2026-05-13 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 713 days from 2024-05-31 to 2026-05-13. Pushes: 27 total, peak 5 in a day. Pull requests: 0 total, peak 0 in a day. Issues: 3 total, peak 1 in a day. Comments: 6 total, peak 2 in a day. Stars: 7 total, peak 2 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 |
|---|---|---|---|---|
| fraz0815 | 33 | 27 | 0 | 4 |
| viniciusfischer | 3 | 0 | 0 | 2 |
Recent activity
Latest issues, pull requests and releases
- Releasefraz08152025-11-18 22:53gdctl-v2
- Issue comment#3fraz08152025-11-12 08:12gdm-settings are not applied to login sceen
- Releasefraz08152025-11-09 13:24gdctl release
- Issue comment#2fraz08152024-09-28 19:33No active output found. on Wayland
- Issue#2fraz08152024-09-28 19:33No active output found. on Wayland
- Releasefraz08152024-09-28 19:32Wayland only
- Issue comment#2viniciusfischer2024-08-19 05:32No active output found. on Wayland
- Issue comment#2viniciusfischer2024-08-19 05:32No active output found. on Wayland
- Issue#2viniciusfischer2024-08-19 05:31No active output found. on Wayland
- Issue#1fraz08152024-07-11 21:43Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
- Issue comment#1fraz08152024-07-11 21:32Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
- Issue comment#1fraz08152024-07-11 21:22Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
- Releasefraz08152024-06-01 00:53terminal only
- Releasefraz08152024-05-31 03:42beta
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 7 stars here means stars gained during the window, not the repo's star count.