dotnet-gha-publish

Generate GitHub Actions workflows to publish .NET packages and container images.

Updated Aug 16, 2025
One-click install
npx skills add https://github.com/dodyg/blue-nile-pds --skill dotnet-gha-publish-dodyg
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotnet-gha-publish
Source: https://github.com/dodyg/blue-nile-pds/tree/main/.agents/skills/dotnet-gha-publish
Command: npx skills add https://github.com/dodyg/blue-nile-pds --skill dotnet-gha-publish-dodyg

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually configuring GitHub Actions for .NET artifact publishing is error‑prone and time‑consuming, especially when handling NuGet packages, container images, signing, and SBOMs.

Core Features & Use Cases

  • NuGet package publishing to nuget.org and GitHub Packages, with tag‑based versioning.
  • Container image builds for GHCR, Docker Hub, and Azure Container Registry, supporting Dockerfile and SDK‑based workflows.
  • Artifact signing for both NuGet packages and containers, and SBOM generation for supply‑chain transparency.
  • Conditional triggers based on semantic version tags or GitHub releases, enabling automated release pipelines.

Quick Start

Invoke the dotnet‑gha‑publish skill to automatically generate GitHub workflow files that publish NuGet packages and container images when a tag is pushed.

Frequently Asked Questions about dotnet-gha-publish

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate .NET NuGet package publishing in GitHub Actions?

Automate .NET NuGet package publishing by generating GitHub workflow files that use setup-dotnet and secret credentials to push packages to nuget.org or GitHub Packages triggered by semantic version tags.

Can I build and push .NET container images to multiple registries using GitHub Actions?

Yes, .NET container images can be built and pushed to GHCR, Docker Hub, and Azure Container Registry using docker/build-push-action, supporting both Dockerfile and SDK-based workflows triggered by tags or releases.

How does artifact signing and SBOM generation work for .NET GitHub Actions releases?

Artifact signing and SBOM generation for .NET releases are handled by the workflow files, applying signing to both NuGet packages and container images while generating SBOMs for supply-chain transparency during the automated publish process.

What's the best way to trigger a .NET release pipeline for both packages and containers?

The best way to trigger a .NET release pipeline is by using conditional triggers based on semantic version tags or GitHub releases, which automates the simultaneous publishing of NuGet packages and container images.

Do I need specific GitHub Actions secrets configured to publish .NET packages and containers?

Yes, publishing .NET packages and containers requires appropriate secret credentials configured in GitHub Actions to authenticate with target registries like nuget.org, GHCR, Docker Hub, or Azure Container Registry.

Why does manually configuring GitHub Actions for .NET publishing often fail?

Manually configuring GitHub Actions for .NET publishing is error-prone because it requires correctly orchestrating setup-dotnet, docker/build-push-action, signing, and SBOM generation across multiple registry targets.