Package: git-sizer
Version: 1.5.0-3build1
Architecture: arm64
Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
Original-Maintainer: Debian Go Packaging Team <team+pkg-go@tracker.debian.org>
Installed-Size: 2560
Depends: libc6 (>= 2.34)
Built-Using: golang-1.21 (= 1.21.0-1), golang-github-cli-safeexec (= 1.0.1-1), golang-github-davecgh-go-spew (= 1.1.1-3), golang-github-pmezard-go-difflib (= 1.0.0-3), golang-github-spf13-pflag (= 1.0.6~git20210604-d5e0c0615ace-1), golang-golang-x-sync (= 0.2.0-1), golang-gopkg-yaml.v3 (= 3.0.1-3), golang-testify (= 1.8.1-1)
Section: vcs
Priority: optional
Homepage: https://github.com/github/git-sizer
Description: compute various size metrics for a Git repository
 git-sizer computes various size metrics for a Git repository, flagging
 those that might cause problems or inconvenience. For example:
 .
  • Is the repository too big overall?
  • Does the repository have too many references (branches and/or tags)?
  • Does the repository include too many objects?
  • Does the repository include gigantic blobs (files)?
  • Does the repository include many slightly different large text files?
  • Does the repository include gigantic trees (directories)?
  • Does the repository have many identical files?
  • Does the repository include absurdly long path names?
  • Are there other bizarre and questionable things in the repository?
    • Annotated tags pointing at one another in long chains?
    • Octopus merges with dozens of parents?
    • Commits with gigantic log messages?
 .
 git-sizer can help to reveal the problems described above.
