Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

What `git lfs migrate info` output means?

Tags:

git

git-lfs

When I run git lfs migrate info --everything on a repository I get the following output:

... clipped
migrate: Examining commits:  99% (3622/3647)                                  migrate: Examining commits: 100% (3647/3647), done
*.json  56 MB     739/739 files(s)      100%
*.py    54 MB   2382/2382 files(s)      100%
*.ps1   9.4 MB    468/468 files(s)      100%
*.stl   5.3 MB        4/4 files(s)      100%
*.js    3.4 MB      45/45 files(s)      100%
  1. What does the size mean? For example the 56 MB for *.json
  2. The 739 is probably the number of files, what what the first means and what the second means? (x/y - what is x, what is y?)
  3. 100% - percent of what?
like image 254
Ido Ran Avatar asked Oct 15 '18 19:10

Ido Ran


People also ask

What does Git LFS migrate do with large files?

I thought that git lfs migrate rewrote the history of a repo so that specified large files were kept in LFS. Perfectly true. This means that the repo should get smaller, because it doesn't directly contain all versions of large files. Not exactly true.

What is import in Git LFS?

IMPORT The 'import' mode migrates large objects present in the Git history to pointer files tracked and stored with Git LFS. If --include or --exclude (-I, -X, respectively) are given, the.gitattributes will be modified to include any new filepath patterns as given by those flags.

What is LFS track in Git?

git lfs track will add the files tracked by Git LFS to .gitattributes. It is important to add .gitattributes to Git. Tracking files are not automatically converting these files from your Git history or other branches. 4. Migrate Git History

How does Git-LFS-migrate work?

If not given, git-lfs-migrate (1) will migrate the currently checked out branch. If any of --include-ref or --exclude-ref are given, the checked out branch will not be appended, but branches given explicitly will be appended. The 'import' mode migrates large objects present in the Git history to pointer files tracked and stored with Git LFS.


1 Answers

  1. The size is how many bytes the files in the repository with that extension that are not currently stored in LFS and match the criteria specified in the info command take up. Since your only criterion is --everthing, that's everything in your repo.

  2. The first number is the number of matched files with that extension, while the second number is all the files in your selected commits with that extension. If you throw in the --above= restriction you can see the difference.

  3. The percentage is just the ratio from the numbers in your second question.

like image 194
Stop Harming the Community Avatar answered Oct 31 '22 17:10

Stop Harming the Community