Lars Schneider

@TestStefan Very good question! This approach only covers merged changes. Unmerged branches need a special treatment that is outside the scope of this workshop. But we can help with that...

@toddocon That looks good in general. The 200MB file might be a good candidate for Git LFS.

@alubchuk your repo looks really good. Again the 20MB file might be a good candidate for LFS. In general I recommend to use LFS for files >1MB which are changed...

@onetrickwolf 521 MB files is definitely a candidate for LFS.

@toddocon You have a lot of compiled libraries like `dll`, `lib`, `so` in your repo. If possible it would be good to move that to an artifact store or use...

@toddocon I don't know what `dn` files are... but all of them in your repo are larger than 500kb (the default cut off)... and in total they consume 1GB in...

The first 3 lines of each of those could be interesting: ``` directories-all-sizes.txt directories-deleted-sizes.txt extensions-all-sizes.txt extensions-deleted-sizes.txt path-all-sizes.txt path-deleted-sizes.txt ```

@toddocon These apps are *just* present in the history. They are not in the HEAD commit but you carry around the data with every clone. In the next section we...

``` ==> extensions-all-sizes.txt extensions-deleted-sizes.txt path-all-sizes.txt

@thomas-schuster your repo looks perfect!