ci: Purge documentation CDN cache #1105
Merged
+21
−3
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
thomass-dev
force-pushed
the
cdn-documentation
branch
from
e0b420a to
70c5797
Compare
thomass-dev
changed the title
thomass-dev
force-pushed
the
cdn-documentation
branch
5 times, most recently
from
17ed382 to
fcba013
Compare
thomass-dev
changed the title
thomass-dev
force-pushed
the
cdn-documentation
branch
from
607b317 to
9b48d74
Compare
thomass-dev
force-pushed
the
cdn-documentation
branch
2 times, most recently
from
5b6d6ef to
4383ba9
Compare
jerome-probabl
approved these changes
Jan 14, 2025
waridrox
pushed a commit
to waridrox/skore
that referenced
this pull request
Apr 15, 2025
To fix the documentation access latency on S3, @jerome-probabl has added a CDN with a 24-hour policy. This PR intends to purge the CDN cache after each documentation deployment.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To fix the documentation access latency on S3, @jerome-probabl has added a CDN with a 24-hour policy.
This PR intends to purge the CDN cache after each documentation deployment.