New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prevent big files from being merged to the master with CI/CD #1372
Comments
Added the CI for this and testing it in #1376, however there are some problems with the sizewatcher, might use smt different if it won't be solved. Current policy of the check: |
I think we should also clear the big files from history while we're at it. Clearing the history is easy with bfg like in #813, however we should back it up with CI or we get big files back. I say we remove unnecessary files with >3MB from history, and have ban against them. If there is a gif or image, let them get uploaded to cloud in the future, as a policy. Don't want to go overkill about this, let me hear your thoughts as well. @aliabd, @aliabid94 , @abidlabs. We might want to clean only recent history to not touch the big part of the history, though touching old history is not a big problem either. Another alternative would be not caring about the git size and letting git run wildly :D
|
Definitely we should clean the history one last time. The last 13 files above are >100MB |
I'm fine adopting a policy for images and gifs but we should explore where that would affect performance on eg the website |
@aliabid94 and @abidlabs do you agree as well? |
Sounds good |
I think that's fine for the python library, but I also don't want to overcomplicate things if there are a a few GIFs used for the README. Is there anywhere else we use a GIF? |
Abubakar used unsplash before, and it would work for README. Not sure about the website performance though. Probably would not affect it. |
Sizewatcher was faulty and did not serve our needs, thus got removed from the repo. see |
Even if having a big repo size is not a major problem, it is not nice to maintain in the long run. Both from the perspective of new user git clones or git pulls taking too long or repo taking too much space. Could not find any tool to serve our needs on this issue, will try to solve it with github actions when I find the time. Any help is most welcome 😸 |
I have searched to see if a similar issue already exists.
Find or write a CI tool to warn or report about introduced size difference by PRs.
The text was updated successfully, but these errors were encountered: