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

Don't create default forests if custom forests are defined #164

Closed
rjrudin opened this issue May 10, 2017 · 0 comments
Closed

Don't create default forests if custom forests are defined #164

rjrudin opened this issue May 10, 2017 · 0 comments
Assignees
@rjrudin
Milestone
2.7.0

Comments

@rjrudin
Copy link
Contributor

rjrudin commented May 10, 2017

Creating this issue to capture something that was fixed in this commit:

45a027b

DeployDatabaseCommand is now smart enough to check for custom forests, and if they're found, default forests are not created.
@rjrudin rjrudin self-assigned this May 10, 2017
@rjrudin rjrudin added this to the 2.7.0 milestone May 10, 2017
@rjrudin rjrudin closed this as completed May 10, 2017
rjrudin pushed a commit that referenced this issue May 10, 2017
#164 Fixing test for custom forests, was ignored
ef30dc8
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@rjrudin rjrudin

Labels
None yet
Projects
None yet
Milestone
2.7.0
Development

No branches or pull requests
1 participant
@rjrudin