4 ms·
This is pretty interesting, but I don't know how useful it would be for me. Part of why I feel that way would be just because I don't have those use cases. I g
by lolsal 10y ago
This is pretty interesting, but I don't know how useful it would be for me. Part of why I feel that way would be just because I don't have those use cases.
I guess part of it is I don't use GitHub as a UI to my repos either. When I want to find this information out I go exploring with log/blame.
- sdesol 10y agoThe heatmaps and the graphs in general, or more to help you orient yourself, when having to deal with a lot of information. They make it very easy to view activity across multiple files, branches and repos at once. For me personally, I mainly stick with the "Changes tree", which I prefer to use over log/blame. I'm particular not a fan of using blame, if I need to trace the history for a file, since it can get disorienting. I use what I've dubbed as rapid diffing, which makes it easier to see how a file evolved. Here's an example. https://gitsense.com/rapid-diffing.mp4 https://gitsense.com/rapid-diffing.mp4