Skip to content
This repository was archived by the owner on Dec 19, 2020. It is now read-only.

Changing fork of extant dependency confuses wit update #190

Open
hcook opened this issue Dec 14, 2019 · 0 comments
Open

Changing fork of extant dependency confuses wit update #190

hcook opened this issue Dec 14, 2019 · 0 comments

Comments

@hcook
Copy link

hcook commented Dec 14, 2019

If I have a grandchild dependency checked out, but then its parent (my child) dependency's manifest was changed to point to a fork of that grandchild repo, seems that wit update tries to find the target commit in the original (already present?) grandchild repo instead of fetching the forked grandchild repo and looking for it there, and so fails.

If I manually delete the grandchild dependency from the workspace, then wit update correctly refetches it and the target commit from the private fork.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant