When using the Gitingest web UI, if a user clicks on a nested file (e.g., src/gitingest/cloning.py) in the "Directory Structure" view to exclude it, only the filename (e.g., cloning.py) is added to the "Exclude" input field. This is insufficient for the backend to correctly exclude the file, as it expects the full relative path (e.g., src/gitingest/cloning.py).
Manually typing the full relative path into the "Exclude" field works as expected.