Description

This PR adds a new action designed to free up space on runners before builds. Inspired from https://github.com/easimon/maximize-build-space, but it outdated and not working reliably anymore.

TODO:

• test with Sunshine
• fix dotnet on macOS
• fix homebrew removal
• remove more:
  • "You are running out of disk space" Error. How can I fix this? actions/runner-images#2840 (comment)
  • Add remove-large-packages option easimon/maximize-build-space#20
  • You are running out of disk space. The runner will stop working when the machine runs out of disk space. Free space left: 72 MB. How to fix this ? actions/runner-images#10386
  • https://github.com/endersonmenezes/free-disk-space
  • https://dev.to/mathio/squeezing-disk-space-from-github-actions-runners-an-engineers-guide-3pjg
  • https://stackoverflow.com/questions/75536771/github-runner-out-of-disk-space-after-building-docker-image
  • https://carlosbecker.com/posts/github-actions-disk-space/

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Unit tests have been added or updated for any new or modified functionality

AI Usage

• None: No AI tools were used in creating this PR
• Light: AI provided minor assistance (formatting, simple suggestions)
• Moderate: AI helped with code generation or debugging specific parts
• Heavy: AI generated most or all of the code changes