Your work is saved in the browser’s local storage until you commit it. The editor doesn’t clone the repository, but instead uses the GitHub Repositories extension to carry out most of the functionality that you will use. The web-based editor runs entirely in your browser’s sandbox. You’ve now got immediate access to the wide variety of editing features of VS Code, to perform updates on any file in that repo you’re in. Then, it’s time for MAGIC! Press the period key (.) on your keyboard and watch VS Code load up in the current browser window, with the file you were looking at over on. Open up and browse to the /Src folder to find YAML source code files for your Canvas app screens. Note: you will now have irreversibly linked your app to GitHub, so don’t do this for any “real” app just yet.Īfter linking the repo Power Apps will automatically copy all of the app source code there. Create a GitHub repo, then enable the experimental feature in Canvas app settings.

What are the steps needed? First, we completely everything in Timo’s first blog post. (Grab this MP4 video if the GIF animation doesn’t show up properly.)

In short, what this allows you to do is skip all of the local configuration steps and launch an instance of VS Code directly from a GitHub repo – in your browser. I’m not sure how many people are yet aware of the really magical feature that GitHub offers: the v web-based editor.

What doesn’t feel quite as amazing for a low-code guy like me is the steps needed for configuring the local Visual Studio Code client to connect with a GitHub repo.

You can read this blog post from my FF colleague Timo Pertilä to see how it looks like for app makers: Power Apps and Git version control. The experimental feature for connecting Power Apps Canvas apps with Git version control is pretty amazing.

Visual studio code online editor