The Phantom Quota: Reclaiming GitHub Actions Storage for Peak Software Developer Efficiency

In the fast-paced world of software development, optimizing every aspect of our workflow is crucial for maintaining high software developer efficiency . Yet, sometimes, hidden costs and inefficiencies lurk in unexpected corners. A recent discussion on the GitHub Community forum, initiated by user jefflongo , brought to light a perplexing issue: an organization hitting its GitHub Actions storage quota despite not running any actions for months and having artifact expiration configured. This scenario isn't just a minor inconvenience; it's a drain on resources, budget, and ultimately, developer focus. The Phantom Quota: When "Expired" Doesn't Mean Gone Jefflongo's dilemma was straightforward: an email warning about nearing their Actions storage quota, with usage reports showing approximately 45 gigabyte-hours per day from a single repository. The confounding factor? This repository hadn't executed any actions in over 10 months. Its few old workflow runs had artifacts explicitly set to exp