Conversation
Member
Author
|
Still working on getting the timestamps right for the old commits. |
jacobgkau
force-pushed
the
avif-lfs-fix
branch
2 times, most recently
from
b62e88b to
d422683
Compare
leviport
approved these changes
Apr 14, 2026
jackpot51
approved these changes
Apr 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This should've been done in #347 when the first AVIF images were added to the repo, but it wasn't. As a result, 14 MB of AVIF files are now in the master branch's history.
To address this, the five commits before this (starting with 43e25e5) have been retroactively modified to place .avif files in LFS. The last commit adds the capitalized extension to the list to match the others.
A GitHub admin will need to force-push this branch to master. This will eliminate that 14 MB from the repo's history so it doesn't take that space up forever. (Otherwise, it would stick around in the history even if we converted the files to LFS pointers in the current commit.)