-
Notifications
You must be signed in to change notification settings - Fork 62.1k
Correct cache eviction policy #38744
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Caches are evicted based on access time, not creation time.
Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines. |
How to review these changes 👓Thank you for your contribution. To review these changes, choose one of the following options: A Hubber will need to deploy your changes internally to review. Table of review linksNote: Please update the URL for your staging server or codespace. The table shows the files in the
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server 🤖 This comment is automatically generated. |
Thanks for opening a PR! I'm going to double check with Support that this is accurate, and then hopefully we'll be able to get it rolling. |
@me-and Thanks for being patient! It took longer than I thought it would to get an answer on this, but I'll get it added to the merge queue once checks are passing. |
Thanks very much for contributing! Your pull request has been merged 🎉 You should see your changes appear on the site in approximately 24 hours. If you're looking for your next contribution, check out our help wanted issues ⚡ |
Caches are evicted based on access time, not creation time.
Why:
Closes: #38743
What's being changed (if available, include any code snippets, screenshots, or gifs):
I noted an inconsistency with GitHub Actions Cache messaging with GitHub Support in ticket 3452653, where Arthur confirmed that this documentation is wrong.
Check off the following: