Generally no as this is an intentional limitation in GitHub. The reason for this limitation is that git (general git, not GitHub) stores every version of each file. Therefore having multiple revisions of large files will make the repository bloat and increases the clone and fetch times for other users of a repository (see GitHub Help - Working with large files).
The way GitHub recommends working with large files is using Git LFS (Large File Storage), generally explained as:
... an open-source extension to Git that allows you to work with large
files the same way as any other text
With Git Large File Storage, you and your repository's contributors
can clone large files from the Git command line, open pull requests,
and comment on the diffs. It's the ideal solution for pushing files to
GitHub that are larger than 100 MB.
(see GitHub documentation - versioning large files).
As a general recommendation (not necessarily related to GitHub) the best practice would be not to work with big files, and consider other alternatives to your specific case.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…