Due to GitHub LFS, this repo got completely clogged and unable to be worked on within only 4 days this month, all because we had one new contributor for a short amount of time.
As a result, I tried multiple ways to get rid of LFS and to push a clean non-LFS version, but since in the past we had files that were above the LFS file size limit in github, that was not possible.
The two options would be to delete and recreate the repo, or force push a clean commit with the files as they were. I chose to do the latter as we'd lose stars and issues.
Right now Staple is not buildable as I need to handle some of the binary dependencies some other way. I will be looking into this ASAP as I dislike leaving the repo in such a state, but at least it's workable again.
The way GitHub LFS works doesn't make any sense - LFS is billed by bandwidth now rather than space used, and the billing is pushed all the way on the repo owner, rather than whoever is using Github LFS. As a result this makes open source projects using Github LFS completely unusable, as even CI can drain the LFS budget.
I wish there was a better way to do this, but at least it's the least destructive way of doing this.
Due to GitHub LFS, this repo got completely clogged and unable to be worked on within only 4 days this month, all because we had one new contributor for a short amount of time.
As a result, I tried multiple ways to get rid of LFS and to push a clean non-LFS version, but since in the past we had files that were above the LFS file size limit in github, that was not possible.
The two options would be to delete and recreate the repo, or force push a clean commit with the files as they were. I chose to do the latter as we'd lose stars and issues.
Right now Staple is not buildable as I need to handle some of the binary dependencies some other way. I will be looking into this ASAP as I dislike leaving the repo in such a state, but at least it's workable again.
The way GitHub LFS works doesn't make any sense - LFS is billed by bandwidth now rather than space used, and the billing is pushed all the way on the repo owner, rather than whoever is using Github LFS. As a result this makes open source projects using Github LFS completely unusable, as even CI can drain the LFS budget.
I wish there was a better way to do this, but at least it's the least destructive way of doing this.