remove inadvisable-metadata-backup script from repo#4754
Merged
Conversation
lindseydew
approved these changes
Jun 4, 2026
|
Seen on image-loader, metadata-editor, thrall, cropper, media-api (merged by @andrew-nowak 8 minutes and 57 seconds ago) Please check your changes! |
|
Seen on auth, usage (merged by @andrew-nowak 9 minutes and 1 second ago) Please check your changes! |
|
Seen on collections, leases (merged by @andrew-nowak 9 minutes and 7 seconds ago) Please check your changes! |
1 similar comment
|
Seen on collections, leases (merged by @andrew-nowak 9 minutes and 7 seconds ago) Please check your changes! |
|
Seen on kahuna (merged by @andrew-nowak 11 minutes and 8 seconds ago) Please check your changes! |
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
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.
What does this change?
This script was created for a one-off purpose, and is not likely to be run again. If we did need to run it again, it'd be nice if we didn't have to recreate it from scratch, so we've held onto it. However because it's in a production repo, we're somewhat on the hook for keeping it up to date.
We've moved the script to archived repo https://github.com/guardian/grid-inadvisable-metadata-backup for posterity, and removed from this repo so it's not being flagged as requiring dependency updates or containing vulnerable code.
How should a reviewer test this change?
How can success be measured?
Who should look at this?
Tested? Documented?