Forking this repository didn't solve the issue, which I believe is a bug of GitHub because forking some repo should use my Git LFS limits, not from the original repo.
I wrote this issue to inform you that some people may encounter issues with cloning your repo, and forking your repos will not solve their problems.
$ git clone https://github.com/randolphcyg/gowireshark.git
Cloning into 'gowireshark'...
remote: Enumerating objects: 14005, done.
remote: Counting objects: 100% (1989/1989), done.
remote: Compressing objects: 100% (1127/1127), done.
Receiving objects: 100% (14005/14005), 79.15 MiB | 15.41 MiB/s, done. 12016
Resolving deltas: 100% (5941/5941), done.
Updating files: 100% (6808/6808), done.
Downloading libs/libpcap.so.1 (1.2 MB)
Error downloading object: libs/libpcap.so.1 (c70bf5a): Smudge error: Error downloading libs/libpcap.so.1 (c70bf5a9379985c368e257b30359b886506f4c442052bf1cd4436660279eea8c): batch response: This repository is over its data quota. Account responsible for LFS bandwidth should purchase more data packs to restore access.
Errors logged to 'D:\Projects\GolandProjects\github\gowireshark\.git\lfs\logs\20230911T002107.9409077.log'.
Use `git lfs logs last` to view the log.
error: external filter 'git-lfs filter-process' failed
fatal: libs/libpcap.so.1: smudge filter lfs failed
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'