tiny-pilot / tiny-pilot/tinypilot
Detect orphaned files automatically
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 291
- PR merge metrics
- No merged PRs in 30d
Description
We recently detected orphaned files that weren’t in use for more than a year.
This could easily happen for all asset classes, like .js or .css files, and not just for images.
We could come up with a solution that would report orphaned files during the build. A simple solution I could think of would be to do a full-text search for the paths of all asset files in the code base. That could theoretically create false alerts, but maybe it works sufficiently. (So maybe worth a shot.)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review pull request #1185 and the repository's build process to understand how orphaned image files were detected. Define how the build should report unused asset files, including JavaScript and CSS files, and determine how false alerts will be handled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, javascript
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100