Outdated files are never deleted
Open
Nobody has claimed this yet.
cat-bug
scope-tool
- Dominant language
- Shell
- Stars
- 5
- Forks
- 3
- Avg merge
- 2d 15h
- Merged PRs (30d)
- 1
Description
Tricky balance because removing a file downstream that has been removed from the MANIFEST may lead to documents that are not buildable. On the other hand, we may also rack up outdated files that in the end will still be used even though they should not be.
Contributor guide
No contributing guide indexed for this repository
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
Start by reading how the DAPS-based documentation workflow uses the MANIFEST and handles files downstream. Clarify when a removed MANIFEST entry should delete an outdated file without making documents unbuildable; done means the cleanup behavior is defined and implemented for both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- build-system, documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100