Skip to content

Management caches instructions appear stale #47009

Backlog

Description

@jsoref

Code of Conduct

What article on docs.github.com is affected?

https://docs.github.com/en/actions/how-tos/manage-workflow-runs/manage-caches

What part(s) of the article would you like to see updated?

The entire section:

Viewing cache entries
You can use the web interface to view a list of cache entries for a repository. In the cache list, you can see how much disk space each cache is using, when the cache was created, and when the cache was last used.

On GitHub, navigate to the main page of the repository.

Under your repository name, click Actions.

Screenshot of the tabs for the "github/docs" repository. The "Actions" tab is highlighted with an orange outline.

In the left sidebar, under the "Management" section, click Caches.

Review the list of cache entries for the repository.

To search for cache entries used for a specific branch, click the Branch dropdown menu and select a branch. The cache list will display all of the caches used for the selected branch.
To search for cache entries with a specific cache key, use the syntax key: key-name in the Filter caches field. The cache list will display caches from all branches where the key was used.

Additional information

Consider https://github.com/github/codeql/actions/runs/44595552732

image

There is no Management section.

There is no caches item.

Click the Workflow file and scroll to https://github.com/github/codeql/actions/runs/44595552732/workflow#L33-L40

      - name: Cache entire extractor
        id: cache-extractor
        uses: actions/cache@v3
        with:
          path: |
            ql/extractor-pack/
            target/release/buramu
          key: ${{ runner.os }}-${{ steps.os_version.outputs.version }}-extractor-${{ hashFiles('Cargo.toml', 'Cargo.lock') }}-${{ hashFiles('shared/tree-sitter-extractor') }}-${{ hashFiles('ql/**/*.rs') }}

it's clearly using a cache.

Note that I checked private repos and it's the same. The cache item has disappeared.

Activity

  1. added
    contentThis issue or pull request belongs to the Docs Content team
    on Nov 19, 2026
  2. added
    triageDo not begin working on this issue until triaged by the team
    on Nov 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    builder personacontentThis issue or pull request belongs to the Docs Content teamtriageDo not begin working on this issue until triaged by the team

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions