docs: remove 190 unreferenced images - #16083
Merged
Merged
Conversation
These are images under docs/ that nothing in the repository references -- roughly 28 MB, accumulated as docs pages were rewritten or deleted without pruning their screenshots. The list was built by searching every tracked image basename across the whole repository, not just docs/, matching literal basenames with a boundary check rather than a regex describing what a filename may contain. That kept eight files that a narrower check would have deleted: three whose names contain "&" and are referenced from the notification docs, and five social icons the root README hotlinks out of docs/assets/images/ through github.com/ghraw. Every image referenced from docs/content still resolves after this change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
paulOsinski
marked this pull request as draft
September 24, 2026 19:36
paulOsinski
marked this pull request as ready for review
September 24, 2026 19:46
blakeaowens
approved these changes
Sep 24, 2026
Maffooch
approved these changes
Sep 24, 2026
devGregA
approved these changes
Sep 24, 2026
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Sep 25, 2026
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
4 participants
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.
Removes 190 image files under
docs/that are not referenced from anywhere in therepository. About 28 MB.
These accumulated the usual way: a docs page is rewritten or deleted and its screenshots
are left behind. The
About_Custom_Dashboard_Tiles_*series is a dozen files from onesuch page.
How the list was built
Every tracked image basename was searched for across the whole repository, not just
docs/— every text file outside.gitandnode_modules, including layouts, datafiles, Hugo shortcodes, Django templates and the root README. An image is on this list
only if no exact reference to it was found anywhere.
Matching is on literal basenames with a boundary check, rather than a regex describing
what a filename may contain. Two rounds of verification caught files that a narrower
check would have deleted:
&(Configure_System_&_Personal_Notifications*.png)are referenced from the notification docs in eight languages.
updated-dojo-chop.png,slack-logo-icon.png,Linkedin-logo-icon-png.png,x_logo.jpg,YouTube-Emblem.png) are referenced fromthe root
README.mdthroughgithub.laiyagushi.com/ghrawURLs pointing intodocs/assets/images/. Deleting those would have broken the images on the project'sGitHub front page.
docs/assets/images/logo.pngis kept as well. Nothing indocs/references it, butthe login and report-cover templates reference a
logo.pngunderdojo/img/, and adelete list is the wrong place to resolve that kind of ambiguity.
The names are unique across the corpus, so basename matching is unambiguous here.
Verification
After deletion, every image referenced from
docs/content/**/*.mdstill resolves — zerobroken references.
Release-note and archived-docs screenshots were never candidates: those are historical
records of what a given version looked like, so they are excluded by design rather than
by accident.
🤖 Generated with Claude Code