- From: Fuqiao Xue via GitHub <sysbot+gh@w3.org>
- Date: Wed, 12 Feb 2025 04:25:21 +0000
- To: public-i18n-archive@w3.org
> also as clearly stated before I am quite in doubt, and also I've already stated several times like last time of this discussion, we should be better to identify what is the exact operation eating LFS bandwidth, since normal or simple 'git clone' or 'git checkout' will not download any of LFS data itself (but just pointer within git repository), and definitely something should happen to eat allowed bandwidth. I'm not sure if this is the reason, but I suspect it is this: > If Git Large File Storage (Git LFS) objects are included in [source code archives](https://docs.github.com/en/repositories/working-with-files/using-files/downloading-source-code-archives) for your repository, downloads of those archives will count towards bandwidth usage for the repository. From https://docs.github.com/en/repositories/working-with-files/managing-large-files/about-storage-and-bandwidth-usage#tracking-storage-and-bandwidth-use . -- GitHub Notification of comment by xfq Please view or discuss this issue at https://github.com/w3c/jlreq/issues/454#issuecomment-2652629412 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 12 February 2025 04:25:22 UTC