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

When running "ml {env} capture", don't overwrite custom #126

Closed
dmcassel opened this issue Aug 26, 2013 · 0 comments
Closed

When running "ml {env} capture", don't overwrite custom #126

dmcassel opened this issue Aug 26, 2013 · 0 comments
Assignees
@dmcassel
Labels
bug capture

Comments

@dmcassel
Copy link
Collaborator

Currently, the capture command will grab everything in the modules database and save it. Change that so that it won't overwrite the custom directory.
@ghost ghost assigned dmcassel Aug 28, 2013
dmcassel added a commit that referenced this issue Aug 28, 2013
@dmcassel
#126 When doing "ml capture", check for existence of application/cust…
b31100e 
…om. If it's already on the filesystem, don't overwrite it.
dmcassel added a commit that referenced this issue Aug 28, 2013
@dmcassel
Updated changelog for #126
40037aa
@grtjn grtjn added the capture label Feb 20, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dmcassel dmcassel

Labels
bug capture
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@grtjn @dmcassel