We are considering migrating our CI infrastructure from a locally hosted Git LFS/Jenkins Pipelines instance to GitHub hosted LFS and GitHub Actions.
We want to know if using actions/checkout with lfs: true will count against our LFS bandwith quota. It seems like it shouldn’t since it is internal bandwidth on GitHub’s network, and with the pricing for LFS bandwith using it with any Actions pipeline would be cost prohibitive.
There is only one answer from GitHub Actions first launched that has contradictory responses, @chrispat said that it will, but @wildone in the comments mentioned that it currently wasn’t charging them.
- What is the official policy on our organization being billed for “outgoing” LFS bandwitdth that is internal to GitHub’s network?
- If it isn’t being billed right now, is that an implementation detail subject to change?