Weird UX on deis create --no-remote about workflow-cli HOT 4 CLOSED

Maybe we can split the difference and add text that indicates, "If you want to add a git remote for this app later, its address is: <address>"?

Yeah or just say "If you want to add a git remote for this app later, use deis git:remote". That feature was introduced later to the workflow-cli scene, and that's even less confusing and probably less taxing on the eyes since it doesn't have a git remote URL dumped to the screen. :)

from workflow-cli.

no remote is created, but we still display the push url so you can reference it elsewhere if you wish. This was part of the original design of --no-remote. :)

It's a feature!

EDIT: perhaps "remote available at" should be re-worded to "No remote was created. You can still push this app to ...". Would that make it more clear?

from workflow-cli.

Ah. So the idea here is that --no-remote means don't create a remote now. I'm informed of what it is because I may want to create a remote myself later.

Got it.

Nevertheless, I think this is a somewhat jarring user experience. The more I have talked to users, the more and more interest I hear in deis pull as their deployment mechanism of choice. (In many cases, people already have CI pipelines that they like and those pipelines output Docker images.) This is a large class of user who won't care about the remote ever. From their perspective, the output of this command is still pretty odd.

Maybe we can split the difference and add text that indicates, "If you want to add a git remote for this app later, its address is:

from workflow-cli.

Yeah or just say "If you want to add a git remote for this app later, use deis git:remote".

We can improve even further by saying:

If you want to add a git remote for this app later, use `deis git:remote -a zanier-undertow`

If you don't specify the app name, as with many other commands, the app name is inferred from the name of the current working directory and most of the time, that's going to yield a remote with a URL like:

ssh://[email protected]:2222/example-go.git

And that's usually going to be wrong.

from workflow-cli.