GITSTATS(1) User Commands GITSTATS(1)NAME
gitstats - git history statistics generator
SYNOPSIS
gitstats [options] <repository dir> <output dir>
DESCRIPTION
gitstats is a statistics generator for git(1) repositories. It examines the repository and produces some interesting statistics from the
history of it. Currently HTML is the only output format.
OPTIONS -c option=value
Override a default configuration value. Defaults can be seen by running gitstats without parameters.
Values:
authors_top
How many top authors to show.
commit_begin, commit_end
Specify a commit range to generate statistics from. You can specify only commit_end limit statistics to a certain commit or another
branch.
max_authors
How many authors to show in the list of authors.
max_domains
How many domains to show in domains by commits.
max_ext_length
Maximum file extension length.
style
CSS stylesheet to use.
FAQ
Q: How do I generate statistics of a non-master branch?
A: Use "-c commit_end=web" parameter.
Q: I have files in my git repository that I would like to exclude from the statistics, how do I do that?
A: At the moment the only way is to use git-filter-branch(1) to create a temporary repository and generate the statistics from that.
AUTHORS
gitstats was written by Heikki Hokkanen and others.
See the git repository at http://repo.or.cz/w/gitstats.git for an up-to-date full list of contributors.
WWW
http://gitstats.sourceforge.net/
SEE ALSO git(1)2012.05.28 2012-05-28 GITSTATS(1)
Check Out this Related Man Page
GIT-REQUEST-PULL(1) Git Manual GIT-REQUEST-PULL(1)NAME
git-request-pull - Generates a summary of pending changes
SYNOPSIS
git request-pull [-p] <start> <url> [<end>]
DESCRIPTION
Generate a request asking your upstream project to pull changes into their tree. The request, printed to the standard output, begins with
the branch description, summarizes the changes and indicates from where they can be pulled.
The upstream project is expected to have the commit named by <start> and the output asks it to integrate the changes you made since that
commit, up to the commit named by <end>, by visiting the repository named by <url>.
OPTIONS -p
Include patch text in the output.
<start>
Commit to start at. This names a commit that is already in the upstream history.
<url>
The repository URL to be pulled from.
<end>
Commit to end at (defaults to HEAD). This names the commit at the tip of the history you are asking to be pulled.
When the repository named by <url> has the commit at a tip of a ref that is different from the ref you have locally, you can use the
<local>:<remote> syntax, to have its local name, a colon :, and its remote name.
EXAMPLE
Imagine that you built your work on your master branch on top of the v1.0 release, and want it to be integrated to the project. First you
push that change to your public repository for others to see:
git push https://git.ko.xz/project master
Then, you run this command:
git request-pull v1.0 https://git.ko.xz/project master
which will produce a request to the upstream, summarizing the changes between the v1.0 release and your master, to pull it from your public
repository.
If you pushed your change to a branch whose name is different from the one you have locally, e.g.
git push https://git.ko.xz/project master:for-linus
then you can ask that to be pulled with
git request-pull v1.0 https://git.ko.xz/project master:for-linus
GIT
Part of the git(1) suite
Git 2.17.1 10/05/2018 GIT-REQUEST-PULL(1)