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

Separate graphcool init and graphcool deploy #706

Closed
schickling opened this issue Sep 30, 2017 · 2 comments
Closed

Separate graphcool init and graphcool deploy #706

schickling opened this issue Sep 30, 2017 · 2 comments
Labels
Milestone

Comments

@schickling
Copy link
Member

I suggest to semantically/functionally separate the graphcool init and the graphcool deploy command. This means that the init command just bootstraps a new project without actually deploying it yet.

@kbrandwijk
Copy link
Contributor

That's a very good idea. I use graphcool init a lot just to boilerplate a local project, but without the need to deploy it, at least right away.

@timsuchanek
Copy link
Contributor

Done in latest preview

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants