posit-dev / posit-dev/publisher
Entrypoint Selector: It's surprising to see something deploy without explicitly clicking a Deploy button
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16
- Forks
- 7
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 31
Description
I'm finding that I don't really expect the actual deploy to occur when I'm using the Entrypoint Selector. It feels like this is a good way to setup your deployment but I think it's missing an actual Deploy button.
In contrast, during the Home View flow, you enter the multi-stepper and complete all the steps, then it returns you to the Home View to "Deploy Your Project".
When using the Entrypoint Selector, can we instead kick back out to the Home View to allow the customer a chance to make any final considerations before clicking "Deploy Your Project"?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the Entrypoint Selector flow and comparing it with the Home View multi-stepper flow. Confirm where deployment currently occurs after entrypoint selection, then verify that the flow returns to Home View and waits for the customer to click "Deploy Your Project".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100