Compute various size metrics for a Git repository, flagging those that might cause problems
The emphasis of this release is making it easy to select exactly what references should be included in the analysis, and also to output counts of references by type (e.g., branches vs. tags vs. pull request heads).
sizer.jsonVersion
sizer.threshold
sizer.names
sizer.progress
--no-branches
(the opposite of --branches
)--no-tags
(the opposite of --tags
)--no-remotes
(the opposite of --remotes
)--notes
/--no-notes
--stash
/--no-stash
--include=PREFIX
, --exclude=PREFIX
--include=/REGEXP/
, --exclude=/REGEXP/
refgroup.REFGROUP.name=NAME
refgroup.REFGROUP.include=PREFIX
refgroup.REFGROUP.includeRegexp=REGEXP
refgroup.REFGROUP.exclude=PREFIX
refgroup.REFGROUP.excludeRegexp=REGEXP
--include=@REFGROUP
, --exclude=@REFGROUP
branches
, tags
, remotes
, pulls
, changes
, notes
, and stash
.branches
and tags
.pipe
package for managing command pipelines. This fixes some error-handling paths.What's new:
git-sizer --help
to return success.git
executable.Internal changes:
What's new:
info/grafts
is deprecated--json-version=2
). Add:
Changes since release 1.1.0:
git-annex
as another possibility (along with Git-LFS) for dealing with large files--version
option to display the version of git-sizer
Fixes:
git-sizer
is not in PATH
Changes since release 1.0.0:
MaxPathDepth
(this probably agrees better with user expectations)Fixes:
This is the first public release of git-sizer
.