-
Notifications
You must be signed in to change notification settings - Fork 24
FIX - Cache key #118
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
base: main
Are you sure you want to change the base?
FIX - Cache key #118
Conversation
Reviewer's guide (collapsed on small PRs)Reviewer's GuideThe workflow’s caching mechanism now appends the CI run number to the cache key, ensuring each run generates a unique cache for golden images rather than reusing stale ones. File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@kayhayen don't merge yet |
That run number however seems unknowable for the using workflow? |
Summary by Sourcery
Include GitHub run number in the cache key for golden images in the update-golden-images workflow to avoid cache collisions
Bug Fixes:
CI: