As of writing, this repository is 180MB to clone, which is outrageously large for the amount of code. For comparison, https://github.com/goblint/analyzer is just 22MB with 14 years of development.
The reason for this size appears to be the .jar and .vsix binary blobs, both over 10MB, being committed. And every change committed to these files will just keep duplicate copies of the binary blobs. Committing their deletion won't delete them from the persistent history. So the only way to cut this repository down to reasonable size is to rewrite git history.
To provide prebuilt artifacts, a GitHub Actions workflow should be added to build and upload them.
As of writing, this repository is 180MB to clone, which is outrageously large for the amount of code. For comparison, https://github.com/goblint/analyzer is just 22MB with 14 years of development.
The reason for this size appears to be the .jar and .vsix binary blobs, both over 10MB, being committed. And every change committed to these files will just keep duplicate copies of the binary blobs. Committing their deletion won't delete them from the persistent history. So the only way to cut this repository down to reasonable size is to rewrite git history.
To provide prebuilt artifacts, a GitHub Actions workflow should be added to build and upload them.