github-actions

Creates Azure-deployable .NET CI/CD workflows with OIDC authentication.

4|1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill github-actions-faysilalshareef
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-actions
Source: https://github.com/FaysilAlshareef/dotnet-ai-kit/tree/main/skills/devops/github-actions
Command: npx skills add https://github.com/FaysilAlshareef/dotnet-ai-kit --skill github-actions-faysilalshareef

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams reliably create secure, repeatable GitHub Actions CI/CD workflows for .NET projects so builds, tests, containerization, and deployments follow organizational best practices and avoid leaked credentials.

Core Features & Use Cases

  • Two-job pipeline pattern: separate build-and-test from build-and-push and deploy to ensure PR checks do not trigger deployments.
  • Azure OIDC authentication: avoid stored credentials by using id-token write permissions and azure/login.
  • Container build and deploy: build Docker images with az acr build, push to ACR, replace tokens in Kubernetes manifests, and deploy to AKS with azure/k8s-deploy.
  • Use Case: Implement CI that runs tests on pull requests and builds, tags, and deploys to production on pushes to main while managing secrets via GitHub environments.

Quick Start

Create a workflow that builds and tests on PRs, builds and pushes a Docker image to ACR, and deploys to AKS on push to main using Azure OIDC for authentication.

Frequently Asked Questions about github-actions

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

FAQPage Schema
How do I set up GitHub Actions CI/CD for a .NET project deploying to Azure?

PR-only checks in GitHub Actions are implemented by creating a two-job pipeline pattern that separates build-and-test from deploy jobs. This ensures pull requests trigger tests without starting deployments.

How does Azure OIDC authentication work in GitHub Actions deployments?

Azure OIDC authentication in GitHub Actions works by using id-token write permissions with azure/login. This avoids storing credentials and prevents leaked secrets during containerization and deployment processes.

Can I use GitHub Actions to build and push Docker images to Azure Container Registry?

Yes, you can use GitHub Actions to build and push Docker images to Azure Container Registry. The workflow uses az acr build to create images and pushes them to ACR before deploying to AKS.

What is the best way to deploy .NET containers to AKS using GitHub Actions?

The best way to deploy .NET containers to AKS using GitHub Actions is by replacing tokens in Kubernetes manifests and using azure/k8s-deploy. This method manages secrets via GitHub environments for secure delivery.

Do I need stored credentials to authenticate GitHub Actions with Azure?

No, you do not need stored credentials to authenticate GitHub Actions with Azure. By implementing Azure OIDC authentication with id-token write permissions and azure/login, you avoid leaked credentials entirely.