[Bug]: deno deploy create broken #933
Description
Problem description
The deno deploy create flow has various bugs that make local, non-GitHub deployment difficult and requires switching to the website.
Steps to reproduce
1/ If I enter deno deploy in a new repo, it only lets me select an existing app, not create a new one. Not sure if this is expected or not, but noting it. There is a minor TUI render buffer issue as I navigate this menu as well.
2/ I switch to instead use: deno deploy create and I see the error:
Usage: deno deploy create [root-path]
# ...
error: Missing required option "--org".
This is unexpected as docs and my memory say there's supposed to be an interactive create mode.
3/ I one by one add arguments until the command proceeds: (--app, --source, --region, --org, --entrypoint)
It then gives me a new error, until I provide: --source local --app-directory . which I needed to use trial-and-error as it wasn't clear from the error (shouldn't these be default?)
4/ The deploy command progresses, but fails due to no entrypoint. It seems that my --entrypoint argument does not propagate to the serverside configuration. I have to manually enter it in app.deno.com.
5/ Finally, I realize I accidentally included a file with an error in it. I delete this file and redeploy, but it seems to be cached and persisted in the app. I have to delete the app and start over.
6/ Now, the app is successfully deployed. Note that even knowing the optimal path now, it still requires navigating to the site each time due to step 4.
Expected behavior
I'd expect the interactive deno deploy flow to work without errors and undocumented behavior, and without requiring navigating to the website to create new apps.
Environment
Deno v2.7.7, macOS
Possible solution
No response
Additional context
No response