[v2] Exclude hidden files from example folder during test file collection #9539
Conversation
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
ashovlin
approved these changes
Jun 10, 2025
kdaily
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the port of CLI v1 of #9530
Description of changes:
Tests cases were failing for the users who use Mac Finder that creates hidden system files such as .DS_Store or ._command-name.rst in the directory. Thus, when the test suite is running, it fails because it encounters a unwanted files in the examples folder that has not a .rst or .txt extension.
Resolution
System-generated files like .DS_Store and other hidden files like .command-name.rst are starting with . followed by the file name, hence while gathering all the files having extension other than .rst file, the files starting with . were ignored, making the test suite free from hidden files.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.