A relatively common case that occurs in my workflow is:
An entire class of file is present in a top-level .gitignore for the repo, eg *.parquet to avoid accidentally committing chunky real data files.
There are a few files in the repo that match the top level .gitignore but have been force added to the repository, eg a .parquet file containing some small sample data for an integration test.
In this scenario, erdtree correctly ignores all of the items in the .gitignore file such as build directories etc.., but unfortunately this means it also skips this kind of force-added test file. A really useful feature for me would be a slightly tighter integration with git, such that erdtree could know not to exclude these force-added files from its listing.
Hi,
Firstly, thanks for the great tool!
A relatively common case that occurs in my workflow is:
.gitignorefor the repo, eg*.parquetto avoid accidentally committing chunky real data files..gitignorebut have been force added to the repository, eg a.parquetfile containing some small sample data for an integration test.In this scenario, erdtree correctly ignores all of the items in the
.gitignorefile such as build directories etc.., but unfortunately this means it also skips this kind of force-added test file. A really useful feature for me would be a slightly tighter integration with git, such that erdtree could know not to exclude these force-added files from its listing.Cheers, Joe