Skip to content

Commit

Permalink
Update link to error
Browse files Browse the repository at this point in the history
  • Loading branch information
styfle authored May 11, 2022
1 parent 2e8c129 commit c4dc7d7
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion docs/advanced-features/ci-build-caching.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ To improve build performance, Next.js saves a cache to `.next/cache` that is sha

To take advantage of this cache in Continuous Integration (CI) environments, your CI workflow will need to be configured to correctly persist the cache between builds.

> If your CI is not configured to persist `.next/cache` between builds, you may see a [No Cache Detected](https://github.com/vercel/next.js/tree/canary/errors/no-cache.md) error.
> If your CI is not configured to persist `.next/cache` between builds, you may see a [No Cache Detected](https://nextjs.org/docs/messages/no-cache) error.
Here are some example cache configurations for common CI providers:

Expand Down

0 comments on commit c4dc7d7

Please sign in to comment.