-
Notifications
You must be signed in to change notification settings - Fork 1k
Use default prune settings during dep init #1404
Comments
I can pick this one up if no one else wants it. 😁 |
It's all yours 🎁 |
definitely want to have this one before we release |
Hey folks, just wanted to drop a quick update. Still planning on getting to this one by the end of this upcoming week/weekend. My original plan was this past weekend but I've been sick 🤒 If this blocking |
Feel better! Also I've updated the OP with the desired default prune settings. |
Excellent! Thank you. That was what I was thinking too -- |
@carolynvs we're just keeping this open until we merge the pending prune branch, right? |
It's just how github works. It doesn't auto-close an issue when a PR is merged into the non-default branch. So once the release branch is merged, then all the issues will be closed. |
Now that prune is (almost) absorbed into ensure, dep init should set some safe prune defaults on the generated manifest. init should also apply the prune options against vendor.
See #952 and #1226 for context.
The text was updated successfully, but these errors were encountered: