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

`diesel setup` should give some indication that it created the migrations dir in its output #177

Closed
sgrif opened this Issue Feb 2, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@sgrif
Member

sgrif commented Feb 2, 2016

Right now it only says that it created the database. The terminal output should indicate that the migrations directory was created as well.

@sgrif

This comment has been minimized.

Member

sgrif commented Feb 2, 2016

/cc @mcasper

@sgrif sgrif added this to the 0.5 milestone Feb 2, 2016

@mcasper mcasper changed the title from `diesel setup` should give some indication that it created the migrations dir in its output to [CLI] `diesel setup` should give some indication that it created the migrations dir in its output Feb 3, 2016

@mcasper

This comment has been minimized.

Collaborator

mcasper commented Feb 3, 2016

@sgrif It already does

$ diesel setup
Created migrations/ directory at: /Users/mattcasper/code/home/test/migrations
Creating database: my_db
@sgrif

This comment has been minimized.

Member

sgrif commented Feb 3, 2016

Strange it wasn't doing that for me.

On Tue, Feb 2, 2016, 11:48 PM Matt Casper notifications@github.com wrote:

@sgrif https://github.com/sgrif It already does

$ diesel setup
Created migrations/ directory at: /Users/mattcasper/code/home/test/migrations
Creating database: my_db


Reply to this email directly or view it on GitHub
#177 (comment).

@sgrif sgrif added the cli label Feb 3, 2016

@sgrif sgrif changed the title from [CLI] `diesel setup` should give some indication that it created the migrations dir in its output to `diesel setup` should give some indication that it created the migrations dir in its output Feb 3, 2016

@mcasper

This comment has been minimized.

@mcasper mcasper closed this Feb 3, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment