In most cases, users should run git gc, which calls git prune.
See the section "NOTES", below.
This runs git fsck --unreachable using all the refs available in
refs/, optionally with additional set of objects specified on the
command line, and prunes all unpacked objects unreachable from any of
these head objects from the object database. In addition, it prunes
the unpacked objects that are also found in packs by running gitprune-packed. It also removes entries from .git/shallow that are not
reachable by any ref.
Note that unreachable, packed objects will remain. If this is not
desired, see git-repack(1).
Do not remove anything; just report what it would remove.
Report all removed objects.
Do not interpret any more arguments as options.
Only expire loose objects older than <time>.
In addition to objects reachable from any of our references, keep
objects reachable from listed <head>s.
In most cases, users will not need to call git prune directly, but
should instead call git gc, which handles pruning along with many
other housekeeping tasks.
For a description of which objects are considered for pruning, see
git fsck's --unreachable option.
This page is part of the git (Git distributed version control system)
project. Information about the project can be found at
⟨http://git-scm.com/⟩. If you have a bug report for this manual page,
see ⟨http://git-scm.com/community⟩. This page was obtained from the
project's upstream Git repository ⟨https://github.com/git/git.git⟩ on
2017-03-13. If you discover any rendering problems in this HTML ver‐
sion of the page, or you believe there is a better or more up-to-date
source for the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original man‐
ual page), send a mail to email@example.com
Git 2.7.0.rc1.5.gf3a 12/17/2015 GIT-PRUNE(1)