dotnet-gha-publish

To publish a NuGet package from GitHub Actions, you can automate the process by triggering workflows on Git tags or GitHub Releases, using actions/setup-dotnet to push packages to nuget.org or GitHub Packages with stable and pre-release options.

Pushing a .NET Docker image to GHCR or DockerHub from GitHub Actions involves using docker/build-push-action to build and deploy container images, supporting both Dockerfile-based and SDK container publish methods across registries like GHCR, DockerHub, and ACR.

Yes, you can generate an SBOM and sign .NET artifacts in a GitHub Actions workflow by leveraging NuGet package signing and sigstore/cosign, which secures releases and provides Software Bills of Materials for supply chain transparency.

The best way to trigger conditional publishing for .NET releases in GitHub Actions is by configuring workflows to activate on Git tags matching patterns like v*.*.* or GitHub Release events, ensuring artifacts are published only when intended.

Yes, the GitHub Actions publishing workflow supports pushing NuGet packages to both nuget.org and GitHub Packages simultaneously, allowing you to distribute stable and pre-release versions across different registries in a single workflow run.

You need to use cosign when publishing .NET container images from GitHub Actions to sign the artifacts and ensure supply chain security, providing verifiable provenance and generating an SBOM for the distributed images.