delete-action-cache

KO | EN

gitlite — search

#javascript #python #hacktoberfest #ai #llm #android #machine-learning #nodejs #awesome #kubernetes #pytorch #security #mcp #openai

delete-action-cache

(★ 9)

Automatically delete GitHub Actions cache entries to manage your repository's 10GB cache storage limit.

delete-action-cache Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

[![Test](https://github.com/toshimaru/delete-action-cache/actions/workflows/test.yml/badge.svg)](https://github.com/toshimaru/delete-action-cache/actions/workflows/test.yml)

# Delete Action Cache

Delete GitHub Actions cache with ease.

![OG image](https://raw.githubusercontent.com/toshimaru/delete-action-cache/main/img/delete-cache-action.png)

## 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)

## Supported Events

- `pull_request`
- `pull_request_target`
- `workflow_dispatch`
- `schedule`
- `push`

delete-action-cache

delete-action-cache Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

delete-action-cache

delete-action-cache Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README