How tell accurate LFS repo size before commit or push?

[Jonathan]

Hi,

We are using a repo to store and distribute art source files (team is very spread out and source control amazing). It works great, except when a certain file type is not tagged as LFS, the repo stops working and its very hard to fix. There are a multitude of art file extensions, so it can be easy to miss adding one to the .gitattributes file. Especially if somebody sends you a package with content that you usually don't work with.

Is there a way for users to determine the size of the what the repo would be when it's pushed? When are files tagged with the LFS pointers, can I force a refresh or does to only happen when committed/ pushed?
i.e: When tagged with LFS pointers the local repo can be 40gb but the Bitbucket is 80mb.....if a user can check before pushing and see that the repo will be 3gb instead of 80mb, then we can determine that a file type hasn't been tagged/ and we have some detective work to do. 

Cheers,

Jonathan