git-heatmap-1.0.1 is not a library.
git-heatmap
simple but customizable heatmap for your local git repos written in rust.

Install
Using cargo
- run the following command
cargo install git-heatmap
From source using cargo
- clone the repository
cdinto the repository- run
cargo install --path ., cargo will build a release build and install it, for more info check the cargo-install docs
Usage
# can be ran in any directory that is a valid git repository
# use any local repository from your system
# supports multiple repository
# set what branch to check
# if no -b flag is given all local branches of the repository will be checked
# can also just pass the branches if you're already in a repository
# manually set which branches to check (separated by space)
# supports checking different branches per repository however
# the number of -b flags needs to match the number of -r flags
# an empty string can be passed for the -b flag so all branches get checked
# or to comply with the same number of branch lists per repo lists rule from above
# alternatively you can simply pass a root directory and let the program search for all git projects
# do be warned that doing so means you're losing the customization aspect of choosing
# which branches should be checked per repo, in this case all branches will be checked.
# when using the --root-dir option you can also ignore folders of repos you don't want to count
# by default merges are counted so using --no-merges ensures they won't be counted
# splits the heatmap per month instead of one big chunk
# by default it colors every day based on which one the maximum number of commits in a visible day
# shading all the others accordingly, with by-amount it will instead color each day based on
# the amount of commits in that day
# filter by one or multiple authors (respecting the .mailmap settings)
# without an -a flag all authors will be checked
# choose from when to start the checking
# if no --since flag is given it will start the search one year from the current date
# if no --until date is given it will check for either 365 days since the start date or
# until the current day, depending on which one is closer
# or choose a time span, both --since and --until must use a YYYY-MM-DD format