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 has been archived by the owner on Sep 9, 2020. It is now read-only.
Running dep ensure removes files from vendor/ that is doesn't manage.
For example, I had a third-party shell script contained under vendor, and of course the manifest file from the vendor tool I was previously using. Both were deleted.
AFAIU, dep assumes complete control of vendor/, and may indeed blow things away if it feels like it. @sdboyer is this correct? If yes, my intuition is to document that better, somehow.
Yep, @peterbourgon is correct - we treat vendor/ as entirely volatile. It's very hard to do otherwise and keep the tool consistent - especially before we have #121 figured out.
Running
dep ensure
removes files fromvendor/
that is doesn't manage.For example, I had a third-party shell script contained under
vendor
, and of course the manifest file from the vendor tool I was previously using. Both were deleted.Experienced with dep version 76df5ce.
The text was updated successfully, but these errors were encountered: