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.
In pulling together #644, I noticed that hack/validate-vendor.bash isn't working correctly. It currently runs dep ensure to check for diffs in vendor/ against HEAD; the problem is, if the solving inputs are the same for what's in HEAD and what's in Gopkg.lock, then it won't actually write vendor back out.
With the current command set, there's no way to override this behavior. The new spec does have a flag, -vendor-only, that will force it to write out vendor. Until then, we'd have to hack it to ensure we're always getting the right check - e.g., awk Gopkg.lock to drop the memo field before running dep ensure.
The text was updated successfully, but these errors were encountered:
In pulling together #644, I noticed that
hack/validate-vendor.bash
isn't working correctly. It currently runsdep ensure
to check for diffs invendor/
against HEAD; the problem is, if the solving inputs are the same for what's in HEAD and what's inGopkg.lock
, then it won't actually writevendor
back out.With the current command set, there's no way to override this behavior. The new spec does have a flag,
-vendor-only
, that will force it to write outvendor
. Until then, we'd have to hack it to ensure we're always getting the right check - e.g., awkGopkg.lock
to drop thememo
field before runningdep ensure
.The text was updated successfully, but these errors were encountered: