Does actions/checkout count against Git LFS bandwidth usage?

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.

So:

  1. What is the official policy on our organization being billed for “outgoing” LFS bandwitdth that is internal to GitHub’s network?
  2. If it isn’t being billed right now, is that an implementation detail subject to change?

It would be nice if the policy on this was clarified in the documentation somewhere (like the page on billing for GitHub LFS usage or billing for GitHub Actions) instead of being buried in the forum.

Thank you for your question. Based on my test, after I checked out a 142MB LFS file in my workflow run, the Git LFS Data bandwidth is still showing 0. I have contacted github engineering team , when they give me response, I will update here as soon as possible. 

@jaydenmilne  I have confirmed that actions/checkout is counted into Git LFS bandwidth usage. 

The answer is that every download for every purpose is counted against LFS usage. The SyncAssetUsage job is what computes this data, and it knows nothing about Actions or other special cases.

You could check the LFS usage in your organization settings > Billing page.

What I need to mention is that as the SyncAssetUsage job is a singleton, it runs every so many minutes to process data, and that results in a slight processing delay in Billing page.

2 Likes

Thank you for looking into this for me and the thorough response! It would be nice if this were reflected in the official documentation so people don’t have to hunt through the community forum to find it. Is there someone else I shoud contact to give feedback on the documentation?

And for what it’s worth, it would be very nice if it Actions didn’t count against your LFS bandwidth :wink:

3 Likes

I have already asked to declare that on official document. 

For your requirement:  it would be very nice if it Actions didn’t count against your LFS bandwidth 

I would encourage you to share your idea in the Feedback form for GitHub Actions

1 Like

It’s inconceivable to me that LFS pulls during GitHub Actions would count towards LFS bandwidth… first… you would assume its within GitHub’s own networks… so why am I paying for them to tranfser files between their own devices?

Second, GitHub Packages that are pulled during GitHub Actions do not count towards their bandwidth… so why the difference in billing policy?

I think LFS bandwidth used within actions should be at least counted with smaller ratio since it should be using internal network bandwidth.

As a workaround to save LFS bandwidth, try checking out without lfs option, cache .git/lfs and run git lfs pull after actions/cache step.