There is a staging instance you can use: https://stg.pagure.io to test things including this. I do not have a proper answer. My gut feeling is that we'll have the same limit as what git itself supports, worst case the UI won't be able to render it but the data itself should be fine.

Note that I'd be more than interested in knowing the outcome of your tests so we can see where/how we can improve pagure :)

Also, you're speaking about commit size or file size? I figure git-lfs integration may help with the later, but I don't know for the former since I'm not sure what it means.

So, I think that pushing such a big object would be fine, but very suboptimal (git is absolutely not optimized for huge objects).
In addition to that, python wheel's are binary objects, another thing git isn't ideal for, because it doesn't delatify those.
Do remember that if you commit things like these to the repo, anyone who clones the repo will need to pull the object down, whether they want to or not.

Personally, I would suggest to use the Pagure Releases system for these files, but I do not see a reason why you couldn't commit them.

Note especially that even if you remove the object in a later commit, or you make a small change to it, anyone cloning the repository will need to pull down both of the entire files, and tehy will never be removed.

The only limit currently is disk space we have available, we are not enforcing any limit currently.

I tested a 1.2GB iso commit on stg.pagure.io and it went fine.

I agree with @puiterwijk that releases might be a better place for them, but you can check them into git with all the caveats noted above.

There may be pagure git-lfs integration at some point also.

Does that answer the question? Or is there anything else we can help with here?

I'll go ahead and close this now, feel free to reopen or file a new ticket if you have any further questions we can assist with.

:japanese_castle:

Thanks for testing this out, we have not yet reached the point where we commit such huge files.