uses: name: npm install, build and test
# Checks-out your repository under $GITHUB_WORKSPACE, so your job can access it Triggers the workflow on push or pull request The actions definition in the master branch is similar but publishes to the marketplace without the -pre-release switch. If the pre-release branch is being built then use vsce to publish to the marketplace with the -pre-release switch. Upload the built extension as an artifact. The yaml is bellow, or here if you prefer. The GitHub actions definition is fairly self-explanatory. I’ll make any fixes or improvements in updates to the pre-release before merging the code to the release version and publishing to the marketplace. That way I will get the new pre-release myself from the marketplace and use it in my daily work. I want to get the feature into the pre-release version of the extension on the marketplace quickly. If anyone else finds the extension useful as well then that’s a bonus. I also want to have a little fun with a side-project – learn a little typescript, practice some CI/CD, GitHub Actions and Application Insights. I want to write some new feature and start working with it in a pre-release myself to find any issues before I release it. I use the extension pretty much every day at work so I am my own biggest customer. Test it and make it available for others to test.What am I trying to achieve? I want to have a short turn around of: AL-Go for GitHub) – so it might be worth a look after all. Then again, Microsoft are increasingly using GitHub for AL projects themselves (e.g. If you’re only here for the AL / Business Central content then you might want to give this one a miss. This post is going to be a bit of a brain dump about developing my VS Code extension, branching strategy for pre-releases and releases and using GitHub actions to stitch it all together.
0 kommentar(er)
