Saving the binary testdata/https-request/https-request with git will increase the size of repository

[Laitr0n]

Describe the bug
The binary file testdata/https-request/https-request is currently saved directly in Git. Frequent updates to this binary will cause the repository size to grow progressively larger, potentially leading to performance issues.

To Reproduce
Same as described above.

Expected behavior
The binary file should be managed using Git LFS to prevent excessive growth in repository size.

Screenshots
None.

Information (please complete the following information):
None.

[hengyoush]

Thanks for the suggestions. Are you willing to send a PR for this?

[Laitr0n]

Sure. Assign to me.

[Laitr0n]

Hi @hengyoush,

I’ve encountered a couple of issues while working on migrating the file to LFS:

1. GitHub does not support pushing LFS objects to forked repositories
   According to the GitHub documentation, LFS objects cannot be pushed to forks. To migrate files to LFS successfully, write access to the upstream repository will be necessary to store the LFS objects properly.

2. Tracking files does not retroactively convert them to LFS
   Simply tracking files in LFS does not convert existing files that are already part of the repository's history. The only way to migrate old files is by rewriting the commit history, as outlined in the Git LFS migration tutorial.
   This process is intrusive, as it modifies the commit history. Is this approach acceptable? If so, I may need to further familiarize myself with the procedure or collaborate with someone experienced in LFS migrations for public repositories.

If you have any opinion, please let me know.

[hengyoush]

Thanks a lot for the detailed analysis and write up.

Looks like write access to the repository is needed. I will follow up on this later.