Skip to content

Conversation

@tossnet
Copy link
Contributor

@tossnet tossnet commented Aug 21, 2025

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • My contribution adds a new instruction, prompt, or chat mode file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, or chat mode with GitHub Copilot.
  • I have run node update-readme.js and verified that README.md is up to date.

Description

Added new instructions on best practices for Azure DevOps pipeline YAML files in azure-devops-pipelines.instructions.md. Sections include general guidelines, pipeline structure, build best practices, test integration, security considerations, deployment strategies, variable and parameter management, performance optimization, monitoring and observability, template reusability, and branching and triggering strategies. An example YAML pipeline structure and a list of common anti-patterns to avoid have also been added.


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New chat mode file.
  • Other (please specify):

Additional Notes


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

Added new instructions on best practices for Azure DevOps pipeline YAML files in `azure-devops-pipelines.instructions.md`. Sections include general guidelines, pipeline structure, build best practices, test integration, security considerations, deployment strategies, variable and parameter management, performance optimization, monitoring and observability, template reusability, and branching and triggering strategies. An example YAML pipeline structure and a list of common anti-patterns to avoid have also been added.
Copilot AI review requested due to automatic review settings August 21, 2025 19:54
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR adds comprehensive instructions for Azure DevOps pipeline YAML best practices to help developers create well-structured, secure, and maintainable CI/CD pipelines. The instructions cover essential areas including pipeline structure, security, deployment strategies, and performance optimization.

Key changes:

  • New instruction file providing detailed Azure DevOps pipeline guidance
  • Updated README.md to include the new instruction entry
  • Comprehensive coverage of pipeline best practices with practical examples

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
instructions/azure-devops-pipelines.instructions.md New instruction file containing comprehensive Azure DevOps pipeline YAML best practices with example structure and anti-patterns
README.md Added entry for the new Azure DevOps pipeline instructions in the table of contents

@aaronpowell aaronpowell merged commit f9aefd9 into github:main Aug 21, 2025
2 checks passed
iletai pushed a commit to iletai/awesome-copilot that referenced this pull request Sep 3, 2025
* Added instructions for Azure DevOps pipelines

Added new instructions on best practices for Azure DevOps pipeline YAML files in `azure-devops-pipelines.instructions.md`. Sections include general guidelines, pipeline structure, build best practices, test integration, security considerations, deployment strategies, variable and parameter management, performance optimization, monitoring and observability, template reusability, and branching and triggering strategies. An example YAML pipeline structure and a list of common anti-patterns to avoid have also been added.

* fix following the copilot's comments

---------

Co-authored-by: Christophe Peugnet <christophe.peugnet@outlook.fr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants