Gitinspector Files

Major release with a new HTML theme, support for multiple repositories and many fixes.

What is new

• Several repositories can be analyzed in one run, merged into a unified report.
• A responsive HTML theme of our own, with a light and a dark mode, a default and a terminal look, sortable tables, a search box, and diverging bars, timeline heat maps and file rails in place of the pie charts. It carries no third party libraries at all.
• Minor authors are folded into a single row until the reader asks for them, and ?theme=, ?mode= and ?minor= open a report in a given view straight from the link.
• JSON output format, next to HTML, XML and plain text.
• New -M/--forcemonths option that shows both monthly and weekly statistics together with -w.
• Go, PHP, Rust, Swift and TypeScript are analyzed by default and get metrics, with comment recognition for those and for Robot Framework, Lilypond, JSX, CSV and TSV files.
• A cognitive complexity metric next to the cyclomatic one, charging a branch for how deeply it is nested rather than counting them all alike.
• Dutch, Korean, Portuguese and Russian translations.
• Native executables for Linux, macOS and Windows, a Dockerfile for those who would rather not install anything, and example reports published on GitHub Pages.

Changed output

• "Rows" are now called "lines" throughout the output; the JSON and XML keys rows and modified_rows were renamed accordingly.
• The table of changes ends with a total row, author emails are included in the JSON and HTML output, and the analyzed branch of each repository is named.

Fixes

• Commits on merged branches are no longer lost during analysis, blamed lines follow the newest name of an author, and files without an extension are blamed when asked for with * or **.
• Vertical bars in author names, emails and file names, empty author names, and characters outside ASCII anywhere no longer break the analysis or the output.
• A commit that only changes whitespace no longer aborts the run.
• Running out of memory while starting git is survived with fewer processes instead of an exception, and an error inside an analysis thread, such as an invalid exclusion pattern, is reported instead of hanging gitinspector.
• A git executable that cannot be started, a terminal encoding Python has no codec for, an argument naming a missing directory, and a run outside a git repository are all reported in a sentence rather than a traceback; --version and --help answer anywhere.
• Runs on Python 3 again and keeps running on Python 2.7, with no line buffering warnings from Python 3.8 and later.
• The test suite runs on every supported Python version and on Windows and macOS through GitHub Actions, including tests that check the reports against statistics gathered straight from git.

Downloads

The executables carry the interpreter, the report templates and the translations, and need nothing but git on the machine; each is built on the platform it targets. The Debian package installs on Debian 7 and later and on Ubuntu, in a Python 2 and a Python 3 flavour, and the rpm on Fedora.

An example report is at https://ejwa.github.io/gitinspector/examples/gitinspector_output.html and the manual at https://github.com/ejwa/gitinspector/blob/master/docs/gitinspector.html.