Summary
The releases/ directory contains ~76 PNG screenshot files that add 150–200 MB to every git clone. These files are no longer used in the README/CHANGELOG (since v3.36+), but they remain in git history, increasing clone times and CI/CD bandwidth costs for all contributors.
Proposed Solution
- Add
releases/ to .gitignore to prevent future commits of these files
- Optionally: use
git filter-repo to remove the files from git history (this would require coordination since it rewrites history and affects all forks/PRs)
Benefits
- Faster
git clone for new contributors
- Reduced CI/CD bandwidth and storage
- No functional impact — the screenshots are not used in the current version
Notes
I've already applied local workarounds in my fork (.gitignore, .git/info/exclude, git rm --cached). Happy to help with the implementation if the maintainers agree on the approach.
Summary
The
releases/directory contains ~76 PNG screenshot files that add 150–200 MB to everygit clone. These files are no longer used in the README/CHANGELOG (since v3.36+), but they remain in git history, increasing clone times and CI/CD bandwidth costs for all contributors.Proposed Solution
releases/to.gitignoreto prevent future commits of these filesgit filter-repoto remove the files from git history (this would require coordination since it rewrites history and affects all forks/PRs)Benefits
git clonefor new contributorsNotes
I've already applied local workarounds in my fork (
.gitignore,.git/info/exclude,git rm --cached). Happy to help with the implementation if the maintainers agree on the approach.