From 68a79ff4a179d29ee92cb4f1073bf4dc88fb9abd Mon Sep 17 00:00:00 2001 From: Charlie Marsh Date: Thu, 24 Oct 2024 19:08:48 -0400 Subject: [PATCH] Format --- README.md | 13 +++++-------- 1 file changed, 5 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 60e5db6..709c8ef 100644 --- a/README.md +++ b/README.md @@ -168,14 +168,11 @@ It defaults to `setup-uv-cache` in the `TMP` dir, `D:\a\_temp\uv-tool-dir` on Wi ### Disable cache pruning -By default, the cache is pruned after a run, which means that all pre-built wheels are removed from -the cache -([documentation](https://docs.astral.sh/uv/concepts/cache/#caching-in-continuous-integration)). By -default, the uv cache is pruned after every run, removing pre-built wheels, but retaining any wheels -that were built from source. On GitHub-hosted runners, it's typically faster to omit those pre-built -wheels from the cache (and instead re-download them from the registry on each run). However, on -self-hosted or local runners, preserving the cache may be more efficient. See the -([documentation](https://docs.astral.sh/uv/concepts/cache/#caching-in-continuous-integration)) for +By default, the uv cache is pruned after every run, removing pre-built wheels, but retaining any +wheels that were built from source. On GitHub-hosted runners, it's typically faster to omit those +pre-built wheels from the cache (and instead re-download them from the registry on each run). +However, on self-hosted or local runners, preserving the cache may be more efficient. See +the[documentation](https://docs.astral.sh/uv/concepts/cache/#caching-in-continuous-integration) for more. If you want to persist the entire cache across runs, disable cache pruning with the `prune-cache`