31–40 of 42 posts
If you think this is useful, you might also like codeatlas.dev and its Github Action ( https://github.com/codeatlasHQ/codebase-visualizer-action ). It currently does not support per-contributor activity, but we put a lot of effort into making the diagrams beautiful to look at and the basic approach of using treemaps for visualisation seems very similar. In fact, could be cool to collaborate on this, DM me if interest…
Otherwise looks really cool.
https://github.com/nixos/nixpkgs/ would be a great benchmark for a tool like this :) One of the larger repos on github, close to half a million commits by a large set of contributors to thousands of files.
WakaTime just released the same feature 4 days ago using IDE activity instead of commits. [0] Scroll to the bottom to see the bubble chart screenshot. [0] https://wakatime.com/blog/58-chatgpt-prototyped-our-new-feat...
If you think this is useful, you might also like codeatlas.dev and its Github Action ( https://github.com/codeatlasHQ/codebase-visualizer-action ). It currently does not support per-contributor activity, but we put a lot of effort into making the diagrams beautiful to look at and the basic approach of using treemaps for visualisation seems very similar. In fact, could be cool to collaborate on this, DM me if interest…
The OP works on Git. This project only works on Microsoft GitHub.
Edit: based on your profile I see you're quite anti Microsoft for some reason. I think one doth protest too much in this case though.
git log --pretty=format: --name-only | sort | uniq -c | sort -rg | head -n 30How much faster are your benchmarks using WAL mode? https://www.sqlite.org/wal.html
I experimented earlier to push the limits of SQLite inserts and wrote a blog post[0] about it. We can apply some of the learnings here. I reviewed the OP's code and did some benchmarks; SQLite is not the bottleneck here. The code first generates the commit info from the git log, prints that to stdin [1] and the python script reads from it one by one in a loop [2]. Each of the commit info is written to SQLite. So, wit…
Earlier quoted context omitted.
The OP works on Git. This project only works on Microsoft GitHub.
Are you sure ? I don't have a chance to test right now but from the brief look i had there's nothing specific for GitHub.com. as i see it uses the git log file. Edit: based on your profile I see you're quite anti Microsoft for some reason. I think one doth protest too much in this case though.
I wonder if this can be done faster using the same approach as git-filter-repo or bfg. 68 minutes for something like this is a long time. Otherwise looks really cool.
I couldn't resist and threw `gitoxide` at it, and it turned out to be more than 2x as fast (even though it uses way more CPU to do that, there is definitely room for improvement).
The PR which adds the `db-gen` program: https://github.com/jmforsythe/Git-Heat-Map/pull/6