Rob, thank you for your great and detailed post.
We appreciate your time that you spent to describe your whole flow and issues that you are faced with working on deploying your changes in The Welkin Suite IDE.
We have added several tickets for improvements in a frame of this deployment process, and will work on them soon, so our hope is to get your dream a bit closer to reality. Thank you for sharing your feelings about the wizard with us and for bringing this to our attention.
Also if you do not mind, I would like to just share with you how and what for we intended for these features to work, and maybe this knowledge might help you work a bit more comfortable and smoothly with them.
The ‘Deployment to Organization’ feature is intended for deploying/moving files from your current TWS project to another organization, and this is why it includes all of its present settings you were talking about. This is also why at the first step we have that area where you can enter the credentials of another org and this reasoning is also why this is a mandatory stage. The ability to deploy to the same organization here was implemented a bit after this feature first came to life, as a way to have an additional option to use extended settings of this feature when deploying to the same organization.
Also if you don’t mind, I would like to draw your attention to if you need to just update your files on the same organization, you always can use the ‘Deploy objects’ functionality, and this doesn’t require so many additional actions - this feature is implemented specifically for updating your files as you described: make a change, deploy it, and get back to your working process. In this case, the IDE gathers all the changed files (in a frame of the metadata types that could be deployed, not built) and sends them to your org all at once.
Of course, if you use the deploy to organization, as a workaround, to update one file and not to include all the changed files to this process - currently this is a one way to do this.
I would like to let you know that you can be sure that ability to deploy one separate changed file when there are several/a lot of changed ones, will be available in the IDE in one of the next versions - we are sure you will like this. However currently using the deploy to organization as a workaround to update one file and not to include all the changed files to this process is one way to do this.
Also, we are going to consider your suggestions related to quick access for the Deploy button in TWS UI, and I believe we will make it ‘closer’ the same as the Pull button.
Thank you one more time for your post and for your feedback about The Welkin Suite. We are happy to hear that you enjoy the IDE and will be glad to make it better and more convenient.
Have a nice day!