-
Notifications
You must be signed in to change notification settings - Fork 44
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
vendor: remove the vendored dependencies #1418
Conversation
Should we add the |
Codecov ReportAll modified and coverable lines are covered by tests ✅ |
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.
🟥🟥🟥🟥🟥🟥🟥🟥🟥🟥
9cbeed1
to
e05fe2d
Compare
Everything is green, I set this to "ready", what could possibly go wrong? (but in all seriousness, this needs a careful review but I don't see why we need the vendor/ dir anymore in |
All tests had passed but the branch is out of date. :-( |
This PR is stale because it has been open 30 days with no activity. Remove "Stale" label or comment or this will be closed in 7 days. |
This PR was closed because it has been stalled for 30+7 days with no activity. |
Fixed conflicts and reopened. |
There's a conflict again because of #1451, otherwise lgtm! |
Oh no I am so sorry! |
Similar to what we did in `images` in PR#861 (thanks to @achilleas-k) this commit removes the vendoring from image-builder. We don't package image-builder so just like with images we don't need the vendor dir (go.{mod,sum} is fine to re-create the environment).
This command no longer needs to run.
Similar to what we did in
images
in PR#861 (thanks to @achilleas-k)this commit removes the vendoring from image-builder. We don't
package image-builder so just like with images we don't need the
vendor dir (go.{mod,sum} is fine to re-create the environment).
C.f. osbuild/images#1041 and #1402 (comment)