Skip to content
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

Add more info about caching #615

Merged
merged 4 commits into from
Nov 10, 2023
Merged

Add more info about caching #615

merged 4 commits into from
Nov 10, 2023

Conversation

PhilippeMoussalli
Copy link
Contributor

@PhilippeMoussalli PhilippeMoussalli linked an issue Nov 10, 2023 that may be closed by this pull request
Copy link
Member

@RobbeSneyders RobbeSneyders left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

docs/caching.md Outdated Show resolved Hide resolved
docs/caching.md Outdated Show resolved Hide resolved
docs/caching.md Outdated
lead to unpredictable behavior due to
image updates. Moreover, if one component in the pipeline is not cached then caching will be
disabled for all
subsequent components.

### Disabling caching
## Disabling caching
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you move this to the top? Right below

The caching feature is enabled by default.

probably makes most sense.

PhilippeMoussalli and others added 3 commits November 10, 2023 11:06
Co-authored-by: Robbe Sneyders <robbe.sneyders@gmail.com>
Co-authored-by: Robbe Sneyders <robbe.sneyders@gmail.com>
@RobbeSneyders RobbeSneyders merged commit b9c6b66 into main Nov 10, 2023
5 of 6 checks passed
@RobbeSneyders RobbeSneyders deleted the update-caching-doc branch November 10, 2023 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add high level explanation for caching
2 participants