gh-101100: Use list of 'dirty' docs, with warnings, instead of a clean list#103191
Uh oh!
There was an error while loading. Please reload this page.
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.
As suggested in #103116 (comment), keep a "dirty" list of docs with warnings, instead of a "clean" list of docs with warnings.
This means we have a checklist of files to work on to clean, and any new files added to the
Doc/directory would by default be tested with nitpicks enabled.The functionality is essentially the same, the clean docs are
touched and rebuilt.In calculating the clean files:
*.rstfiles fromDoc/Doc/venv/Doc/tools/dirty-files.txtDoc/includes/wasm-notavail.rstandDoc/whatsnew/changelog.rst, which would trigger dirty files to be rebuilt