Correct GitHub Spelling in caching-strategies.md (#1526)
Some checks failed
Tests / build (ubuntu-latest) (push) Successful in 2m18s
Tests / build (macOS-latest) (push) Has been cancelled
Tests / build (windows-latest) (push) Has been cancelled
Code scanning - action / CodeQL-Build (push) Failing after 2m15s
Licensed / Licensed (push) Failing after 0s
Tests / test-save (ubuntu-latest) (push) Successful in 20s
Tests / test-proxy-save (push) Failing after 1m17s
Tests / test-proxy-restore (push) Has been skipped
Tests / test-save (macOS-latest) (push) Has been cancelled
Tests / test-save (windows-latest) (push) Has been cancelled
Tests / test-restore (macOS-latest) (push) Has been cancelled
Tests / test-restore (ubuntu-latest) (push) Has been cancelled
Tests / test-restore (windows-latest) (push) Has been cancelled

GitHub was spelled incorrectly 3 lines under the Understanding how to choose path section
This commit is contained in:
janco-absa 2025-01-06 18:55:00 +02:00 committed by GitHub
parent 1bd1e32a3b
commit 53aa38c736
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

View File

@ -102,7 +102,7 @@ The [GitHub Context](https://docs.github.com/en/actions/learn-github-actions/con
While setting paths for caching dependencies it is important to give correct path depending on the hosted runner you are using or whether the action is running in a container job. Assigning different `path` for save and restore will result in cache miss. While setting paths for caching dependencies it is important to give correct path depending on the hosted runner you are using or whether the action is running in a container job. Assigning different `path` for save and restore will result in cache miss.
Below are GiHub hosted runner specific paths one should take care of when writing a workflow which saves/restores caches across OS. Below are GitHub hosted runner specific paths one should take care of when writing a workflow which saves/restores caches across OS.
#### Ubuntu Paths #### Ubuntu Paths