In a previous post, using GitHub Actions in Visual Studio is as easy as right-click and Publish, we announced the efforts we added to Visual Studio extending our Publish experiences to introduce and assist customers into a repeatable, predictable continuous integration and deployment (CI/CD) environment using GitHub Actions. Our Publish experience today enables many different ways for developers to get their development, staging, or production apps to various endpoints in their local/network environments and directly to their cloud resources in Azure. We want to maintain that experience and offer more through Publish, providing more value to those desiring CI/CD but also introducing the ease of setup of this workflow to existing users of Publish.

As a part of our development we engaged with some of you in our Developer Community, social media, and directly through some 1:1 interactions trying out our prototypes. All of these experiences were valuable to the team to see how different users of Visual Studio – and specifically Publish – interpret and expect things to work when the option of CI/CD using GitHub Actions is available. Some of the key learnings we had from you all were:

• After the Publish wizard exited, customers landed on the summary page unsure of what to do next
• The section “Service Dependencies” was confusing, some customers looked for GitHub Action triggers in there
• The summary page did not explain which triggers were being used by the workflow

#github #vscode