Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

use git index to see force-added files

See original GitHub issue

We’ve received a few reports about people getting confused by dvc pull/etc not detecting their dvc files in configuration with such .gitignore:

/data
!**/*.dvc

as explained by @pmrowla , this is just a nonobvious git behavior and a workaround is:

/data/**
!/data/**/
!/data/**/*.dvc

But dvc list will see those files no problem, because it doesn’t seem to use is_ignore (needs confimation), thus, we should use git index locally as well to detect force-added files even if they are gitignored.

Issue Analytics

State:
Created 2 years ago
Reactions:4
Comments:14 (4 by maintainers)

Top GitHub Comments

2reactions

karajan1001commented, Jul 6, 2021

I think this is enough.

/data/**
!**/*.dvc

1reaction

efiopcommented, Jul 8, 2021

@SebbanSms deps only declare dependencies for that particular stage, they don’t really do data management. Plus, same path could be declared as a dependency in multiple stages/dvc.yaml’s , which is a bit problematic for us right now in terms of mapping of versions (aka md5s), while outs are unique and don’t have that problem. We might reconsider this in the future though.