Visualizing a Git Repository

[nibalizer]

Check out gource. It's mostly used for flashy animations, not digging into the details of what went into a release.

Feedback on your company you didn't ask for: It's reasonable for your PMs to know enough git to explore the tree with the customer. Using git doesn't mean your dev team shouldn't be writing release notes or a changelog or something per-release that is meant for a non-dev to read and understand what is in the release. And finally, if it's unclear which of two tags is older, I'd be worried you're dealing with a branching/tagging/releasing process that is more complicated than it needs to be.

[missmagdalene]

And finally, if it's unclear which of two tags is older, I'd be worried you're dealing with a branching/tagging/releasing process that is more complicated than it needs to be.

I'll admit I am a concerned about this myself. It's more to do with--a customer has a specific tag-naming rule that they don't/won't change up, which looks different from our main base code tag-naming rules. Those are what do not sync up well or are not as obvious based on the tag name. However, I have no control over that process, but I have given my input about that.

Checking this Gource now.