📚 Document caching being enabled automatically

Default behavior of caching is "auto", meaning it's enabled on github-hosted runners. This wasn't obvious at first, and I was wondering why I was getting warnings about cache when I didn't even have it enabled. Hopefully this small documentation update will save some headaches (for those who read the docs at least 😉)
This commit is contained in:
Jeremy Mayeres 2025-02-25 16:52:19 +02:00 committed by GitHub
parent b498c74bf4
commit 7ae02b1b98
WARNING! Although there is a key with this ID in the database it does not verify this commit! This commit is SUSPICIOUS.
GPG key ID: B5690EEEBB952194

View file

@ -156,6 +156,7 @@ are automatically verified by this action. The sha256 hashes can be found on the
If you enable caching, the [uv cache](https://docs.astral.sh/uv/concepts/cache/) will be uploaded to If you enable caching, the [uv cache](https://docs.astral.sh/uv/concepts/cache/) will be uploaded to
the GitHub Actions cache. This can speed up runs that reuse the cache by several minutes. the GitHub Actions cache. This can speed up runs that reuse the cache by several minutes.
Caching is enabled by default on GitHub-hosted runners.
> [!TIP] > [!TIP]
> >