Install with: cargo install gmap
Or on Arch via AUR: yay -S gmap
Repo: https://github.com/seeyebe/gmap
Feedback is welcome. Contributions too. if you’re into Git internals, CLIs, or terminal UX.
Install with: cargo install gmap
Or on Arch via AUR: yay -S gmap
Repo: https://github.com/seeyebe/gmap
Feedback is welcome. Contributions too. if you’re into Git internals, CLIs, or terminal UX.
Do those questions matter to you? They don't matter to me at all, so I'm curious to hear about why they matter to you. What do they matter to you for?
Knowing which code changes frequently or infrequently doesn't actually tell you anything about what code should change, because recency and frequency are not valid proxies for importance.
I guess my question then is why should someone care about these patterns that are explicitly not what's "important"?
You say things like
"can guide refactoring, onboarding"
and
"For some workflows (e.g. legacy cleanup, team handover, bug tracking), that context can be quite valuable."
But those are vague hand-wavy statements that don't explain themselves. I don't understand why it would be valuable for those tasks, and I could use some explanation of what concrete problem is solved by looking at these details.
I'm not sure there's anything better than manually tracing hotpaths and making changes. Maybe an INTERNALS.md to document architecture would be nice. And reading through recent PRs too. Curious about your approach.
It’s still early, but I’d like to evolve it to make those insights more actionable, maybe even link recent PRs, show how files evolved, or highlight ownership boundaries. Feedback like yours helps shape that, so thanks again.
Ok, and code hotpaths are not represented by repo metadata.
seeyebe•6mo ago