repo-visualizer VS Gource

That isn’t to say that the problem is impossible. When I want to learn a codebase, I run it through gource, which visualizes how the structure of the repo changes over time (https://gource.io/). I read the unit tests, and hope that they demonstrate the behavior of the code that is being tested. I run it through repo visualizer to view the static structure of the code (https://github.com/githubocto/repo-visualizer).

A visualization similar to what https://github.com/githubocto/repo-visualizer produces is much easier to look at. I'd use the above tool, but i don't have the ability to use github actions, so looking for something similar.

If you’re curious about more details, the full source code for the repo-visualizer is available on GitHub and its readme lists all available configuration options. Configuration options typically get added underneath the with: step.

The underlying technology, https://gource.io/, has probably been mentioned here before, but it's a superb tool which produces beautiful animations, so deserves another airing.

This is really cool. And as OP pointed out, I really like the pipeline integration. Like when linting catches function-level complexity, but in a cross functional way. I prefer to think of programs in layers where the top layers can import lower layers, but never the other way (and also very cautious on horizontal imports). Something like this would help track that.

From the visualization perspective, it reminds me a lot of Gource. Gource is a cool visualization showing contributions to a repo. You see individual contributors buzzing around updating files on per-commit and per-merge.

https://github.com/acaudwell/Gource

Nešto kao gource?

Yeah, I was completely distracted trying to figure out what `import { Button, icons } from "ui"` was derived from. Looks like `

That being said, I do like the overall idea of animating code changes. Calls back to that old Facebook sketching app[0] that would let us share replays, and I am a fan of the stories that Gource[1] can tell.

Ultimately, though, the sequential text file is a bad metaphor for code. Best thing for it is to split your modules across files.

0. Can't remember the name of it, but something similar is https://sketchtoy.com/

1. https://gource.io/

If the goal is to create a fun animation, then have a look at https://gource.io/ for inspiration.

From https://github.com/acaudwell/Gource

I wonder what your history would look like in Gource: https://gource.io/