git-lfs.github.com | Git LFS website

As described on packagecloud[1], you need to run:

Use the repository files API. No special handling is needed for files that happen to use LFS. It's simply an HTTPS request to the endpoint.

You've already requested the information which should be contained in pkgResult. The content of the file is in the response payload as content encoded in base64.

Just extract the content field from the deserialized JSON and base64 decode it to get the contents of the file.

In addition of ignoring .angular/cache, you can consider using git filter-repo instead of the obsolete git filter-branch or BFG.

That way, you would:

• install git filter-repo (python-based)
• delete any large file in your history: git filter-repo --strip-blobs-bigger-than 2M for instance. (content-based filtering)
• ignore .angular/cache
• force push (git push --force: make sure to notify any collaborator on that repository)

You shouldn't commit your virtual environment env/ at all, as it can be created from any requirements file, i.e requirements.txt.

Instead, add env/ to your .gitignore file, or create one if it doesn't exist. Try to use a .gitignore template here and edit it to your usage.

Installing LFS only affects new commits. You'll have to rewrite the repo to move the old files to LFS as well:

• https://edwardthomson.com/blog/advent_day_23_removing_large_binaries_with_lfs.html

It's safest to do a fresh git clone --mirror for a few reasons:

You can do a mirror clone, which will clone the remote into a bare repository locally so that you don't check out all your large files unnecessarily. It will also get all the remote branches and tags, and set up remote tracking branches so that you can safely perform a force push.

I solved this by the following.

Check your log of commits.

After finding this post, I was able to fix the issue. This post gave me the idea to push the .gitattributes file to the repo before trying to push the video.

I ran git reset commit_hash_before_video to go back to before the video commit and .gitattributes commit. I ran git add .gitattributes git commit -m "added .gitattributes" git push to push that file before pushing the video. Then I ran git add . git commit -m "added video" git push. The video went through.

What is probably the "real" answer is git-lfs like the error message suggests, which github does have support for, but it costs money when over 2GB. If your not in a position that that is available I found this post about how to work around the 100mb file size limit which some have to do with compression which would work well with .fbx files (becuase they are plain text and that compresses well)

Extra note that you left some information in the question that you might potentially want to remove (like your email)

Try flutter clean before committing to git.

because, after flutter clean, build directory will not be there at all..so, no debug APK.