From b6771abf4861bca34a0b5985388b02dad6ae2ff7 Mon Sep 17 00:00:00 2001 From: Zachary Hughes Date: Thu, 5 Jun 2025 14:46:34 -0400 Subject: [PATCH] Update caching-dependencies-to-speed-up-workflows.md just cleaning up some comments and names for the clean up cache docs --- .../caching-dependencies-to-speed-up-workflows.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows.md b/content/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows.md index db93faad61c2..f8a1e7d5e3ef 100644 --- a/content/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows.md +++ b/content/actions/writing-workflows/choosing-what-your-workflow-does/caching-dependencies-to-speed-up-workflows.md @@ -333,7 +333,7 @@ The following example workflow uses `gh cache` to delete up to 100 caches create To run the following example on cross-repository pull requests or pull requests from forks, you can trigger the workflow with the `pull_request_target` event. If you do use `pull_request_target` to trigger the workflow, there are security considerations to keep in mind. For more information, see [AUTOTITLE](/actions/using-workflows/events-that-trigger-workflows#pull_request_target). ```yaml -name: cleanup caches by a branch +name: Cleanup github runner caches on closed pull requests on: pull_request: types: @@ -347,7 +347,7 @@ jobs: steps: - name: Cleanup run: | - echo "Fetching list of cache key" + echo "Fetching list of cache keys" cacheKeysForPR=$(gh cache list --ref $BRANCH --limit 100 --json id --jq '.[].id') ## Setting this to not fail the workflow while deleting cache keys.