-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
RepoDependency: never changed #4209
Conversation
d7cabf1
to
5d57706
Compare
5d57706
to
f2010f7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need a test for this? Otherwise, looks good to me.
@skshetry |
f2010f7
to
5ea6ba3
Compare
5ea6ba3
to
624f2d1
Compare
@skshetry I created test |
with dvc.state: | ||
assert stage.changed_entries() == ([], [], None) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Won't it show up on dvc.status
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IIRC these are not used by status
but by commit
to show prompt message on what's changed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@skshetry is right, in case of commit we check whether changed_checksum
for RepoDependency
changed. Upon status, we actually get the checksum for the file from the external repo, to get information on whether it has been updated.
β I have followed the Contributing to DVC checklist.
π If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here.
β I will check DeepSource, CodeClimate, and other sanity checks below. (We consider them recommendatory and don't expect everything to be addressed. Please fix things that actually improve code or fix bugs.)
Thank you for the contribution - we'll try to review it as soon as possible. π
Fixes #4205