Unexpected $0.01 charge for actions with no private repos

[pimterry]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Misc

Discussion Details

My organization (https://github.com/httptoolkit/) has been charged $0.01 for GitHub Actions in May, but:

• It doesn't have any private repos - literally zero
• The billing report CSV I've just downloaded says net_amount=0 for every row
• I think I have budgets set to $0 with 'stop usage' enabled for everything

The only clue I can see is one row in May's usage that says "<$0.01" instead of just $0 for action storage. I can't see why that's applied though or how it could have happened, as my understanding is that public repo action storage isn't charged.

Obviously I'm not particularly worried about a one cent charge, but I would like to understand where this has come from, in case I'm accidentally going to run up a debt somewhere.

[h3ssan]

About the $0.01 charge: GitHub may apply a temporary authorization hold for usage-based costs in advance, which can appear as a small, seemingly unexplained charge.

[pimterry]

I was sent a full invoice for this though, which seems very unusual for a payment hold like that? A receipt implies an actual payment, I would have thought.

[h3ssan]

Looks like you have charged for a tiny amount (less than 0.01$), but GitHub aggregates tiny charges or rounds up fractional usage to the minimum billable amount (often $0.01).

[pimterry]

I want to know why I was charged though - as far as I'm aware, action storage is always free for public repos. And I have a $0 budget limit. And the CSV with detailed information doesn't list any charges at all. It's very weird!

Basically I'm worried that something is going to start racking up bills so that later months will somehow be far more expensive unexpectedly, and I'm hoping some GitHub staff can confirm where this has come from and why.

[itsfolf]

Having the exact same today with Git LFS Storage. Did someone get their floats wrong?

[pimterry]

Eventually I opened a support ticket and GitHub said:

The engineering team has identified an issue where users were charged a couple cents for metered billing products. I've reversed this charge and the engineering team is working on preventing this from happening again.

So yes - it's a bug. They might refund all of these automatically, but if not just open a support ticket and they'll clean it up for you.