Delete stale renditions when file or focal area changes are detected #24
Conversation
This file contains 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
|
@zerolab I was seeing similar pre-commit job failures on previous PRs when the ruff job was passing. I can only assume they are using different versions or configurations of ruff? |
ababic
changed the base branch from
main
to
fix/force-download-option-causes-typerror
zerolab
approved these changes
Apr 24, 2024
ababic
force-pushed
the
fix/force-download-option-causes-typerror
branch
from
afb5119 to
8b56d31
Compare
ababic
force-pushed
the
feature/delete-renditions-when-file-or-focal-area-changes
branch
from
d472b8e to
f29855d
Compare
ababic
changed the base branch from
fix/force-download-option-causes-typerror
to
main
|
pre-commit.ci autofix |
for more information, see https://pre-commit.ci
ababic
deleted the
feature/delete-renditions-when-file-or-focal-area-changes
branch
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.
This is typically handled by
wagtail.images.forms.BaseImageFormwhen updating images via the UI, but there's currently nothing in place to handle this when updating model instances directly.