NkwaTambe commented on PR #5922: URL: https://github.com/apache/fineract/pull/5922#issuecomment-4649151282
> > > > > > Hello @adamsaghy , > > > > > > The $102.02 was observed in our organization's GitHub billing and was associated with our public fork of Fineract, not the Apache Fineract repository itself. > > > > > > The fork was consuming a significant amount of artifact and container storage, which is what led us to investigate and make the retention-related changes. > > > > > > > > > > > > > > > We are applying shorter retention as your PR recommended, but my understanding is if you are on public fork of Fineract, the cost might appear, but it is not billable. > > > > > > > > > > > > Thanks for the clarification. I'll double-check the billing details with our team to better understand whether that amount was actually billable or just reported usage. > > > > > > > > > @NkwaTambe Hi > > > Have you had the chance to double check with your team? > > > > > > Hi @adamsaghy > > Yes, I confirmed with our team today that the storage usage was indeed billable and the charges were reflected in our GitHub invoice. > > This is weird. I have checked with multiple people and all of them said: > > * If the repository is public -> No billable charges > * Unless you are using Large runner (anything except the normal available github runner or not public repository), there should not be billable costs.. > > I wonder what might be the reason at your end. > > If you are on public repository, I would reach out to Github and ask them to clarify why it got billed... You could write: Hi @adamsaghy , We're only using the same GitHub-hosted runners as the official Fineract repository (`ubuntu-24.04`, `ubuntu-22.04`, and `ubuntu-latest`). We haven't made any changes to the runner configuration since creating the fork, and we're not using any custom or larger runners. Given that, we'll take a closer look at our organization-level GitHub billing and settings to better understand where the charges are coming from. Thanks for your insights. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
