https://github.com/toshimaru/delete-action-cache
Automatically delete GitHub Actions cache entries to manage your repository's 10GB cache storage limit.
https://github.com/toshimaru/delete-action-cache
github-actions
Last synced: 5 months ago
JSON representation
Automatically delete GitHub Actions cache entries to manage your repository's 10GB cache storage limit.
- Host: GitHub
- URL: https://github.com/toshimaru/delete-action-cache
- Owner: toshimaru
- License: mit
- Created: 2024-04-03T00:49:21.000Z (about 2 years ago)
- Default Branch: main
- Last Pushed: 2025-12-06T01:25:12.000Z (7 months ago)
- Last Synced: 2025-12-09T16:25:47.320Z (7 months ago)
- Topics: github-actions
- Homepage: https://github.com/marketplace/actions/delete-action-cache
- Size: 123 KB
- Stars: 8
- Watchers: 1
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://github.com/toshimaru/delete-action-cache/actions/workflows/test.yml)
# Delete Action Cache
Delete GitHub Actions cache with ease.
## Motivation
GitHub Actions cache is limited to 10GB per repository. If you use a lot of cache storage, you may see the following warning message:
> **Approaching total cache storage limit (XX GB of 10 GB Used)**
>
> Least recently used caches will be automatically evicted to limit the total cache storage to 10 GB. [Learn more about cache usage.](https://docs.github.com/actions/using-workflows/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy)
The documentation says:
> GitHub will remove any cache entries that have not been accessed in over 7 days. There is no limit on the number of caches you can store, but the total size of all caches in a repository is limited to 10 GB. Once a repository has reached its maximum cache storage, the cache eviction policy will create space by deleting the oldest caches in the repository.
[Usage limits and eviction policy - GitHub Docs](https://docs.github.com/en/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows#usage-limits-and-eviction-policy)
To prevent reaching this limit, it’s essential to delete unused or unnecessary caches automatically.
## Usage
### Delete caches after a pull request is closed/merged
```yml
name: Delete Action Cache
on:
pull_request_target:
types: [closed]
jobs:
delete-cache:
runs-on: ubuntu-latest
steps:
- uses: toshimaru/delete-action-cache@main
```
### Delete caches manually
Use the `workflow_dispatch` event to trigger the action manually.
```yml
name: Delete Action Cache
on:
workflow_dispatch:
jobs:
delete-cache:
runs-on: ubuntu-latest
steps:
- uses: toshimaru/delete-action-cache@main
```
- **Select a branch** from dropdown menu
- Click "**Run workflow**"
- The action deletes the branch caches
See also. [Manually running a workflow - GitHub Docs](https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-workflow-runs/manually-running-a-workflow)
### Schedule cache deletion
Delete caches periodically with the `schedule` event.
```yml
name: delete action cache
on:
schedule:
- cron: '0 3 * * *'
jobs:
delete-cache:
runs-on: ubuntu-latest
steps:
- uses: toshimaru/delete-action-cache@main
branch: my-cache-branch
```
## Inputs
See [action.yml](action.yml)
| Name | Description | Default |
| - | - | - |
| `github-token` | A token for the repository | `github.token` |
| `limit` | The number of caches to delete | 100 |
| `branch` | The branch name where the cache is stored | - (default branch) |
| `repo` | The repository name | `github.repository` |
## Supported Events
- `pull_request`
- `pull_request_target`
- `workflow_dispatch`
- `schedule`
- `push`