GitHub Actions Retention Now Covers Checks, Runs, and Statuses
GitHub Actions has expanded its retention policy. Checks, workflow runs, and statuses are now automatically deleted according to the same retention settings as artifacts and logs, improving automated cleanup and storage management for developers.
What changed?
The GitHub Actions retention setting now controls the lifecycle of checks, workflow runs, and statuses, in addition to artifacts and logs. When these records exceed the configured retention period, they are automatically removed. This expanded policy applies to all repositories on github.com, with a maximum retention period of 90 days for public repositories.
Why does it matter to an everyday developer?
Previously, only artifacts and logs were subject to automated cleanup, leaving checks, workflow runs, and statuses to accumulate. Developers can now better manage repository size and avoid clutter, as all GitHub Actions-related records will be consistently cleaned up using one setting. This helps keep project histories tidy and may reduce potential storage-related issues in large or active repositories.
What can the developer do now?
Developers and repository administrators should review and, if necessary, update their retention settings to ensure they align with organizational or project needs. Note that increasing the retention period will not restore records already deleted under the previous policy. Settings can be managed at the repository, organization, or enterprise level, but public repositories cannot exceed 90 days.
