Initial Content #1
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
AlexanderLanin
requested review from
MaximilianSoerenPollak,
dcalavrezo-qorix,
kgraeper and
nradakovic
There was a problem hiding this comment.
Pull request overview
This PR introduces the initial content for a GitHub Action that provides fast disk cleanup for Ubuntu runners (22.04 & 24.04). The action offers 4 configurable cleanup levels that balance space freed against time taken, using direct rm -rf deletion for speed.
Changes:
- Implements a Node.js-based GitHub Action with 4 cleanup levels (3.7-22.2 GiB in 1-40s)
- Adds comprehensive benchmarking workflow comparing this action against 4 alternatives
- Includes detailed documentation explaining design decisions and trade-offs
Reviewed changes
Copilot reviewed 11 out of 11 changed files in this pull request and generated 9 comments.
Show a summary per file
| File | Description |
|---|---|
| action.yml | Defines the action metadata and input parameters (level 1-4) |
| index.js | Main action logic that performs cleanup based on level selection |
| post.js | Post-action reporting and suggestions based on remaining space |
| scripts/aggregate.py | Python script to aggregate benchmark metrics and generate summary |
| .github/workflows/benchmark-disk-space.yml | Workflow for benchmarking cleanup performance |
| .github/workflows/PR.yml | PR validation workflow to test the action |
| .github/actions/measure-before/action.yml | Composite action to capture baseline metrics |
| .github/actions/measure-after/action.yml | Composite action to measure cleanup results |
| README.md | User-facing documentation with usage examples |
| docs/alternatives.md | Detailed comparison with alternative cleanup actions |
| benchmark.md | Documentation for the benchmark workflow |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
kgraeper
reviewed
Jan 16, 2026
Member
Author
|
no-op feature not tested on self hosted runner. But it looks good. 
|
Member
Author
|
Actually... I just realized... every second action will install/remove stuff on your runners. You should not rely on this one action having a check for that. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After this is merged I would delete the v1 branch, and instead tag this commit as v1.
Tested in eclipse-score/reference_integration#76: