Skip to content
▁▅▆▃▅ Git quick statistics is a simple and efficient way to access various statistics in git repository.
Branch: master
Clone or download
Latest commit 3d86fa9 Mar 5, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
docs Update index.html Dec 7, 2018
tests Changed non-interactive args and fixed main loop Jan 11, 2019
.mailmap
.travis.yml Update .travis.yml Sep 29, 2017
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md Jun 16, 2017
LICENSE Update LICENSE Jan 19, 2019
Makefile Add man page to reinstall target Feb 4, 2019
README.md
git-quick-stats
git-quick-stats.1 add man page Jan 16, 2019

README.md

GIT quick statistics Backers on Open Collective Sponsors on Open Collective Tweet Travis Homebrew package Linuxbrew package

git-quick-stats is a simple and efficient way to access various statistics in git repository.

Any git repository contains tons of information about commits, contributors, and files. Extracting this information is not always trivial, mostly because of a gadzillion options to a gadzillion git commands – I don’t think there is a single person alive who knows them all. Probably not even Linus Torvalds himself :).

screenshot

Table of Contents

Screenshots

Installation

Usage

System requirements

Contribution

FAQ

License

Screenshots

screenshot-3

screenshot-2

Usage

git-quick-stats

Or you can use (non-interactive) direct execution:

git-quick-stats <optional-command-to-execute-directly>

Possible arguments in short and long form:

-r, --suggest-reviewers
    show the best people to contact to review code
-T, --detailed-git-stats
    give a detailed list of git stats
-d, --commits-per-day
    displays a list of commits per day
-m, --commits-by-month
    displays a list of commits per month
-w, --commits-by-weekday
    displays a list of commits per weekday
-o, --commits-by-hour
    displays a list of commits per hour
-A, --commits-by-author-by-hour
    displays a list of commits per hour by author
-a, --commits-per-author
    displays a list of commits per author
-S, --my-daily-stats
    see your current daily stats
-C, --contributors
    see a list of everyone who contributed to the repo
-b, --branch-tree
    show an ASCII graph of the git repo branch history
-D, --branches-by-date
    show branches by date
-c, --changelogs
    see changelogs
-L, --changelogs-by-author
    see changelogs by author
-h, -?, --help
    display this help text in the terminal

Git log since / until

You can set variable _GIT_SINCE, _GIT_UNTIL and limit the git log

export _GIT_SINCE="2017-20-01"
export _GIT_UNTIL="2017-22-01"

then run git quick-stats (affect all stats, except "My daily status" and "Git changelogs" )

Git log limit

You can set variable _GIT_LIMIT for limited output (it will affect: "Git changelogs" and "Branch tree view" )

export _GIT_LIMIT=20

Git pathspec

You can exclude directory from the stats by using pathspec

export _GIT_PATHSPEC=':!directory'

Installation

Unix like OS

git clone https://github.com/arzzen/git-quick-stats.git && cd git-quick-stats
sudo make install

For uninstalling, open up the cloned directory and run

sudo make uninstall

For update/reinstall

sudo make reinstall

OS X (homebrew)

brew install git-quick-stats

Windows (cygwin)

System requirements

  • Unix like OS with a proper shell
  • Tools we use: awk ; cat ; column ; echo ; git ; grep ; head ; seq ; sort ; tput ; tr ; uniq ; wc

Dependences

FAQ

Q: I get some errors after run git-quick-stats in cygwin like /usr/local/bin/git-quick-stats: line 2: $'\r': command not found

A: You can run dos2unix app in cygwin /bin/dos2unix.exe /usr/local/bin/git-quick-stats. This will convert it to Unix format and you then should be able to run it.

Contribution

Want to contribute? Great! First, read this page.

Code reviews

All submissions, including submissions by project members, require review.
We use Github pull requests for this purpose.

Some tips for good pull requests:

  • Use our code
    When in doubt, try to stay true to the existing code of the project.
  • Write a descriptive commit message. What problem are you solving and what are the consequences? Where and what did you test? Some good tips: here and here.
  • If your PR consists of multiple commits which are successive improvements / fixes to your first commit, consider squashing them into a single commit (git rebase -i) such that your PR is a single commit on top of the current HEAD. This make reviewing the code so much easier, and our history more readable.

Formatting

This documentation is written using standard markdown syntax. Please submit your changes using the same syntax.

Tests

codecov

make test

Licensing

MIT see LICENSE for the full license text.

Contributors

This project exists thanks to all the people who contribute.

Backers

Thank you to all our backers! 🙏 [Become a backer]

Sponsors

Support this project by becoming a sponsor. Your logo will show up here with a link to your website. [Become a sponsor]

You can’t perform that action at this time.