这是indexloc提供的服务，不要输入任何密码
Skip to content

docs: clarity for GitHub Actions caching strategies #10583

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 21, 2025
Merged

docs: clarity for GitHub Actions caching strategies #10583

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/site/content/docs/guides/ci-vendors/github-actions.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -229,7 +229,7 @@ Create a file called `.github/workflows/ci.yml` in your repository with the foll

</PackageManagerTabs>

## Remote Caching
## Remote Caching with Vercel Remote Cache

To use Remote Caching with GitHub Actions, add the following environment variables to your GitHub Actions workflow
to make them available to your `turbo` commands.
Expand Down Expand Up @@ -294,9 +294,9 @@ jobs:
</Step>
</Steps>

## Caching with GitHub actions/cache
## Remote Caching with GitHub actions/cache

The following steps exemplify how you could use [actions/cache](https://github.com/actions/cache) to cache your monorepo artifacts on GitHub.
The following steps show how you could use [actions/cache](https://github.com/actions/cache) to cache your monorepo artifacts on GitHub.

<Steps>
<Step>
Expand All @@ -318,7 +318,7 @@ Example `package.json` with a `build` script:

</Step>
<Step>
Configure your GitHub pipeline with a step which utilizes the `actions/cache@v4` action before the build steps of your CI file.
Configure your GitHub pipeline with a step which uses the `actions/cache@v4` action before the build steps of your CI file.

- Make sure that the `path` attribute set within the `actions/cache` action matches the output location above. In the example below, `path` was set to `.turbo`.
- State the cache key for the current run under the `key` attribute. In the example below, we used a combination of the runner os and GitHub sha as the cache key.
Expand Down
Loading