monorepo tooling w/ bi-directional sync; cargo aware
active 2025-11-07 → 2026-08-08 (UTC)
Activity over time
Daily event counts in the loaded window
Line chart, 275 days from 2025-11-07 to 2026-08-08. Pushes: 152 total, peak 9 in a day. Pull requests: 1 total, peak 1 in a day. Issues: 11 total, peak 2 in a day. Comments: 5 total, peak 2 in a day. Stars: 84 total, peak 30 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 |
|---|---|---|---|---|
| loadingalias | 165 | 152 | 1 | 5 |
| solvip | 1 | 0 | 0 | 0 |
| EpicEric | 1 | 0 | 0 | 0 |
| brndnmtthws | 1 | 0 | 0 | 0 |
| deifactor | 1 | 0 | 0 | 0 |
Recent activity
Latest issues, pull requests and releases
- Issue comment#12loadingalias2026-05-22 02:16`cargo rail unify --check` should not require a git repository
- Issue comment#11loadingalias2026-02-19 21:06`cargo rail unify` doesn't actually detect unused dependencies
- Issue#11loadingalias2026-02-19 03:27`cargo rail unify` doesn't actually detect unused dependencies
- Issue comment#11loadingalias2026-02-19 03:26`cargo rail unify` doesn't actually detect unused dependencies
- Issue#11deifactor2026-02-19 01:47`cargo rail unify` doesn't actually detect unused dependencies
- Releasegithub-actions[bot]2026-02-14 23:36v0.10.0
- Releasegithub-actions[bot]2026-02-14 04:57v0.10.0
- Releasegithub-actions[bot]2026-02-11 03:15v0.9.1
- Issue#9loadingalias2026-02-05 20:07Changing `package.publish` requires regenerating `target/cargo-rail`
- Issue#9loadingalias2026-02-05 20:06Changing `package.publish` requires regenerating `target/cargo-rail`
- Issue#10solvip2026-02-01 17:14Option to ignore binary crates?
- Issue#6loadingalias2025-12-23 19:57`error: Crate has path-only dependency` for crate with `publish = false`
- Issue#6loadingalias2025-12-23 19:57`error: Crate has path-only dependency` for crate with `publish = false`
- Issue comment#8loadingalias2025-12-22 18:43Merge dependency features into root crate (hakari-style behavior)
- Issue#8brndnmtthws2025-12-22 16:31Merge dependency features into root crate (hakari-style behavior)
- Releasegithub-actions[bot]2025-12-19 04:41v0.8.1
- Releasegithub-actions[bot]2025-12-19 03:00v0.8.0
- Issue#6loadingalias2025-12-18 04:45`error: Crate has path-only dependency` for crate with `publish = false`
- Issue#7loadingalias2025-12-18 04:45`publish = false` doesn't exclude crate from `--all`
- Issue comment#6loadingalias2025-12-17 04:32`error: Crate has path-only dependency` for crate with `publish = false`
- Releasegithub-actions[bot]2025-12-17 04:28v0.7.3
- Issue#6EpicEric2025-12-16 10:31`error: Crate has path-only dependency` for crate with `publish = false`
- Releasegithub-actions[bot]2025-12-12 13:12v0.5.2
- Releasegithub-actions[bot]2025-12-05 07:13v0.1.0
- Pull request#2loadingalias2025-11-13 05:17
Totals cover only the window loaded into ClickHouse and count events, not GitHub's lifetime totals — 84 stars here means stars gained during the window, not the repo's star count.