Caching is a great way to speed up your CI/CD pipeline. It can be used
to reduce the number of requests to the same URL during consecutive runs. For
example, if you have a lot of links to https://github.com, you can cache the
responses to reduce the load.
Here is an example of how to cache the results of a lychee run.
Caching in GitHub Actions
This pipeline will automatically cache the results of the lychee run.
Note that the cache will only be created if the run was successful.
If you need more control over when caches are restored and saved, you can split
the cache step and e.g. ensure to always save the cache (also when the link
check step fails):