microsoft / microsoft/GitHub-Copilot-for-Azure

Add CI/CD pipeline configuration skill (azd pipeline config, GitHub Actions, Azure DevOps)

Open
#1,002 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

skills untriaged
Dominant language
Python
Stars
250
Forks
204
Avg merge
1d 12h
Merged PRs (30d)
67

Description

## Summary

There is no skill covering CI/CD pipeline setup for Azure deployments. This is a gap identified from an analysis of proposed azd skills (Azure/azure-dev#6501).

## Proposed Skill: pipeline-config

**Trigger scenarios:**
- Setting up CI/CD with \zd pipeline config\
- Generating GitHub Actions workflows for Azure deployments
- Configuring Azure DevOps pipelines
- Setting up service principals, federated credentials, and secrets
- Managing deployment environments and approvals

**Coverage needed:**
- \zd pipeline config\ workflow (provider selection, credential setup)
- GitHub Actions workflow generation (build, test, deploy stages)
- Azure DevOps pipeline YAML generation
- Service principal / federated identity credential guidance
- Secrets management (GitHub Secrets, Azure Key Vault integration)
- Multi-environment deployment patterns (dev/staging/prod)
- Deployment gates and approval flows

**Reference:** The \zure-prepare\ and \zure-deploy\ skills currently do not address CI/CD pipeline configuration. This is independent of the prepare-validate-deploy workflow and should be a standalone skill.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing azure-prepare and azure-deploy skills and the referenced azd pipeline config workflow. Use the issue’s coverage list to assess the standalone pipeline-config scope across GitHub Actions, Azure DevOps, credentials, secrets, environments, and approvals. Done means the skill addresses each listed CI/CD scenario without duplicating the prepare-validate-deploy workflow.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, github-actions, yaml
Domain
ci-cd, cloud, devops
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.