ng-github-actions | using GitHub Actions to test a Angular project | Continous Integration library

I wrote a test to verify the POST was parsed correctly. Here is the endpoint:

I've seen and attempted to follow several examples of how to do this, but they all seem to be for the version of web assembly projects that target .Net 2.1 Standard.

• https://swimburger.net/blog/dotnet/how-to-deploy-aspnet-blazor-webassembly-to-github-pages
• https://www.meziantou.net/publishing-a-blazor-webassembly-application-to-github-pages.htm
• https://www.davideguida.com/how-to-deploy-blazor-webassembly-on-github-pages-using-github-actions/

The project I am attempting to deploy with a github action is targeting .Net 5.0

According to the documentation from MS, "Standalone deployment assets are published into the /bin/Release/{TARGET FRAMEWORK}/publish/wwwroot folder."

https://docs.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly?view=aspnetcore-5.0#standalone-deployment

I'd thought of just giving up on a CI/CD for this and just deploying it manually. However, when I examine this folder, there is no 'publish' folder inside the {TARGET FRAMEWORK} folder. And inside wwwroot, there is nothing resembling what I'd think of as a web site.

So... can anybody give direction on how to achieve this?

I want to have a services section for Github Actions workflow file with a private registry. The simplified config looks like this:

I think I have followed all the steps to deploy Blazor webassembly on GitHub Pages using GitHub Actions which I found from https://www.davideguida.com/how-to-deploy-blazor-webassembly-on-github-pages-using-github-actions/

But it failed at Deploy to Github Pages step

• Set up job (Passed)
• Run actions/checkout@v2 (Passed)
• Setup .NET Core (Passed)
• Publish with dotnet (Passed)
• Deploy to Github Pages (Failed)
• Post Run actions/checkout@v2 (Passed)
• Complete job (Passed)

Here are the error descriptions

I woke up to my GitHub Actions BETA invite this morning (wooo) and have started playing with it, with the aim of migrating some simple build, test and deploy pipelines I currently have running on CircleCI.

I'm still trying to get my head around Actions, but the flow I have in mind is that after a push, the first Action in the workflow will launch a Docker container. Inside that container I'll run some simple build processes such as minimising assets and removing artefacts. The next Action will then run some tests on the build. And the next Action(s) in the pipeline will deploy to one of a number of environments, depending on the branch I pushed to.

I've followed the docs at https://developer.github.com/actions/creating-github-actions/creating-a-docker-container/ and have a rudimentary workflow that launches a Docker container and runs some build commands inside the WORKDIR. I'm also able to run a deployment (via rsync) from inside this WORKDIR too.

However, I'd like to split this into separate steps/Actions, but I can't figure out a way to to this.

Essentially, this would be similar to the CircleCI jobs/workflow model I'm using. However, with CircleCI, the first job runs a build then persists the resulting directory structure throughout the rest of the workflow, like this: