Skip to content
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.

Document the prune command #875

Closed
carolynvs opened this issue Jul 21, 2017 · 4 comments
Closed

Document the prune command #875

carolynvs opened this issue Jul 21, 2017 · 4 comments

Comments

@carolynvs
Copy link
Collaborator

Once #819 is merged, let's add documentation for subpackages to the README and explain how dep treats them. It's a bit confusing right now (before the ensure overhaul) that the lock lists the subpackages but they aren't automatically removed by dep. You must run dep prune to get rid of unused subpackages from vendor.

@sdboyer
Copy link
Member

sdboyer commented Jul 23, 2017

Yes, prune needs its own docs. Though they should also include a note - on both the CLI and whatever we write elsewhere - that we plan to subsume prune into ensure.

@stephenafamo
Copy link
Contributor

Can I work on this? @carolynvs

@carolynvs
Copy link
Collaborator Author

@stephenafamo Yes, please that would be very helpful! ❤️

@sdboyer
Copy link
Member

sdboyer commented Nov 15, 2017

i'm gonna close this one out, as we're on the verge of getting rid of prune anyway.

@sdboyer sdboyer closed this as completed Nov 15, 2017
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants