-
Notifications
You must be signed in to change notification settings - Fork 1k
Description
Description:
When using the -i (include) option with gitingest, specifying a subdirectory (e.g., utils/dme/) only includes files directly within that directory, but does not include files within its nested subdirectories. This behavior is unexpected and limits the usefulness of the include filter, especially for repositories with deeper directory structures.
Example Directory Structure:
testrepo/
├── src/
│ ├── modules/
│ ├── nav/
│ │ ├── nav.txt
│ │ └── nav_grpah.txt
│ └── screen/
│ ├── screen1.txt
│ ├── screen2.txt
│ └── screen3.txt
└── utils/
├── di/
├── dme/
│ ├── dme1.txt
│ └── dme2
└── parser/
Observed Behavior:
Running gitingest /path/to/testrepo/ -i "utils/dme/" does not include files in nested subfolder dme.
Using -i "src/,utils/" works as expected for top-level directories, but specifying a subdirectory like utils/dme/ does not recursively include any files.
Steps to Reproduce:
-
Create a repository with nested directories as shown above.
-
Run:
gitingest /path/to/testrepo/ -i "utils/dme/" -
Observe that only top-level files in utils/dme/ are included, and nested files are omitted.
