Only exclude mkdocs config YAML files. #117
Merged
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.
There was a blanket exclusion of all YAML files introduced to fix issue #9. There are certain use-cases where non-mkdocs YAML files should be included in the documentation - e.g. OpenAPI spec files.
This change only excludes YAML files that are marked as mkdocs config file for the repo being imported.
This passes the existing test "Make sure imported repo's mkdocs.yml isn't in build output".
Fix for issue #107