fix(cache): Add write permissions to clear cache workflow

[AdrienPoupa]

Why:

The gh cache list call needs the write actions permission, otherwise it fails with Error: Resource not accessible by integration..

It was reported here: actions/gh-actions-cache#85

What's being changed (if available, include any code snippets, screenshots, or gifs):

Added the write actions permission to the cleanup cache workflow.

Check off the following:

• A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
• The changes in this PR meet the docs fundamentals that are required for all content.
• All CI checks are passing and the changes look good in the review environment.

[welcome]

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

[Copilot]

Pull Request Overview

This PR adds the required write permissions to the cache cleanup workflow to resolve the "Resource not accessible by integration" error when running the gh cache list command.

• Updated the cleanup job in the caching dependencies workflow file to include the "actions: write" permission.
• Enhances workflow stability by ensuring necessary permissions are set.

[github-actions]

How to review these changes 👓

Thank you for your contribution. To review these changes, choose one of the following options:

• Spin up a codespace
• Set up a local development environment

A Hubber will need to deploy your changes internally to review.

Table of review links

Note: Please update the URL for your staging server or codespace.

The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.

Source	Review	Production	What Changed
actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows.md	fpt ghec ghes@ 3.17 3.16 3.15 3.14 3.13	fpt ghec ghes@ 3.17 3.16 3.15 3.14 3.13

Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server

🤖 This comment is automatically generated.

[Sharra-writes]

Thanks for opening a PR! I'll get this triaged for review.

[github-actions]

Thanks for opening a pull request! We've triaged this issue for technical review by a subject matter expert 👀

[github-actions]

This is a gentle bump for the docs team that this PR is waiting for technical review.

[Sharra-writes]

This looks good, so I'll get it added to the merge queue as soon as checks are passing!

[github-actions]

Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡

[shannonsetzer]

I am not on this website GitHub .. could it be from my boyfriends account where he has access to my account info and password accounts to my website how can I be subscribed to this thread without having an account with GitHub  Sent from Yahoo Mail for iPhone On Friday, May 30, 2025, 4:08 PM, Sharra-writes ***@***.***> wrote: Merged #37953 into main. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[Sharra-writes]

@shannonsetzer This is something that should be taken to the support team, or speak to your boyfriend directly and have him remove your information from his account. No one in this repository is equipped to help with account-related issues, I'm afraid.