You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 19, 2020. It is now read-only.
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.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.The text was updated successfully, but these errors were encountered: