How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/docs/custom-instructions/containerization/copilot-instructions.md
built multiple times without side effects. - Use Docker Compose for local development and testing environments
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/docs/custom-instructions/dotnet/copilot-instructions.md
object-to-object mapping if needed. - Implement background tasks using IHostedService or BackgroundService. ## Testing - Write unit tests using xUnit, NUnit, or MSTest. - Use Moq or NSubstitute for mocking dependencies. - Implement
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/docs/custom-instructions/java/copilot-instructions.md
field injection for better testability. - Leverage Spring's IoC container for managing bean lifecycles. ## Testing - Write unit tests using JUnit 5 and Spring Boot Test. - Use MockMvc for testing
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/localisation/es-es/docs/custom-instructions/java/copilot-instructions.md
vida de beans. ## Pruebas - Escribe pruebas unitarias usando JUnit 5 y Spring Boot Test. - Usa MockMvc para probar capas web. - Implementa pruebas de integración usando @SpringBootTest. - Usa @DataJpaTest para pruebas
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/localisation/fr-fr/docs/custom-instructions/containerization/copilot-instructions.md
effets de bord. - Utilisez Docker Compose pour les environnements de développement local et de test. --- **Avertissement**: Ce document a été localisé par [GitHub Copilot](https://docs.github.com/copilot/about-github-copilot/what-is-github-copilot). Par conséquent
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/localisation/fr-fr/docs/custom-instructions/dotnet/copilot-instructions.md
objet si nécessaire. - Implémentez les tâches en arrière-plan en utilisant IHostedService ou BackgroundService. ## Tests - Écrivez des tests unitaires en utilisant xUnit, NUnit, ou MSTest. - Utilisez Moq ou NSubstitute pour
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/localisation/fr-fr/docs/custom-instructions/java/copilot-instructions.md
parti du conteneur IoC de Spring pour gérer les cycles de vie des beans. ## Tests - Écrivez des tests unitaires en utilisant JUnit 5 et Spring Boot Test. - Utilisez MockMvc pour
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/localisation/ja-jp/docs/custom-instructions/java/copilot-instructions.md
OpenAPI（旧Swagger）を使用する。 ## データアクセスとORM - データベース操作にはSpring Data JPAを使用する。 - 適切なエンティティ関係とカスケードを実装する。 - FlywayやLiquibaseなどのツールでデータベースマイグレーションを使用する。 ## ビルドとデプロイメント - 依存関係管理とビルドプロセスにはMavenまたはGradleのいずれかを使用する。 - 新しいプロジェクトでは柔軟性とパフォーマンスのためGradleを優先する。 - 異なる環境（dev、test、prod）用の適切なプロファイルを実装する。 - 適用可能な場合はコンテナ化にDockerを使用する。 ## 以下のベストプラクティスに従う： - RESTful API設計（HTTPメソッド、ステータスコードなどの適切な使用）。 - マイクロサービスアーキテクチャ（適用可能な場合）。 - SpringのWebFluxを使用したSpringの@Asyncまたはリアクティブプログラミングを使用した非同期処理。 Spring Bootアプリケーション設計でSOLID原則を遵守し、高い凝集性と低い結合度を維持してください
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/localisation/pt-br/docs/custom-instructions/containerization/copilot-instructions.md
construídos múltiplas vezes sem efeitos colaterais. - Use Docker Compose para ambientes de desenvolvimento e teste locais. --- **Aviso**: Este documento foi localizado pelo [GitHub Copilot](https://docs.github.com/copilot/about-github-copilot/what-is-github-copilot). Portanto, pode conter
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/localisation/pt-br/docs/custom-instructions/dotnet/copilot-instructions.md
mapeamento objeto-para-objeto se necessário. - Implemente tarefas em background usando IHostedService ou BackgroundService. ## Testes - Escreva testes unitários usando xUnit, NUnit ou MSTest. - Use Moq ou NSubstitute para mock
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/localisation/pt-br/docs/custom-instructions/java/copilot-instructions.md
testabilidade. - Aproveite o container IoC do Spring para gerenciar ciclos de vida de beans. ## Testes - Escreva testes unitários usando JUnit 5 e Spring Boot Test. - Use MockMvc para testar camadas
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/localisation/zh-cn/docs/custom-instructions/java/copilot-instructions.md
利用 Spring 的 IoC 容器管理 bean 生命周期。 ## 测试 - 使用 JUnit 5 和 Spring Boot Test 编写单元测试。 - 使用 MockMvc 测试 Web 层。 - 使用 @SpringBootTest 实现集成测试。 - 使用 @DataJpaTest 进行存储库层测试。 ## 性能和可扩展性 - 使用 Spring
Microsoft AzureCopilot instructionsAzure/azure-webpubsub/.github/copilot-instructions.md
left over is `sdk/webpubsub-socketio-extension/examples/*/extensions.csproj`: `socketio_e2e.yml` builds Node packages and checks the credential-free test harness on pull requests, with live service tests restricted to pushes to `main`. It does
LangChainCopilot instructionslangchain-ai/langchain-azure/libs/azure-cosmosdb/.github/copilot-instructions.md
this project, we use `poetry` for packaging and dependency management, and `pytest` for testing. The following commands are useful: - **Creating the development environment:** `poetry install --with test,lint,typing` - **Running
LangChainCopilot instructionslangchain-ai/langchain-azure/libs/azure-postgresql/.github/copilot-instructions.md
packaging and dependency management. Similarly, we use `pytest` and `tox` to handle testing and test automation. The following commands/tools are useful for the following purposes: - **Creating the development environment
Microsoft AzureCopilot instructionsAzure/sap-automation/.github/copilot-instructions.md
defines the review dimensions in priority order — correctness, reliability/SRE, security, Azure/SAP domain rules, performance, testing coverage, maintainability — along with the evidence bar and the known false-positive classes for this
MicrosoftCopilot instructionsmicrosoft/mcs-labs/.github/copilot-instructions.md
directly to `main` - **Action**: Remind user to create/switch to feature branch first 2. **Local Testing**: ALWAYS test locally before ANY push - **STOP if**: User tries to push without testing - **Action
AWSCopilot instructionsaws/aws-sdk-net/.github/copilot-instructions.md
that modify code generally require a DevConfig file; limited exceptions include docs-only, tests-only, and build-script-only changes. See `CONTRIBUTING.md` and the `aws-sdk-net-devconfig` skill
imbenrabiCopilot instructionsimbenrabi/Financial-Modeling-Prep-MCP-Server/.github/copilot-instructions.md
reuse). The SDK manages `sessionId`, but caching does not use it. ## Development Workflows ### Testing Strategy - **Framework**: Vitest with comprehensive mocking patterns - **Key Pattern**: Mock external dependencies in test files using
Microsoft AzureCopilot instructionsAzure/aks-mcp/.github/copilot-instructions.md
based on access level ## Development Commands ### Build ```bash go build -o aks-mcp ./cmd/aks-mcp ``` ### Test ```bash go test -v ./... # Run all tests go test -race -coverprofile=coverage.txt -covermode=atomic
Repository-wide instructions for GitHub Copilot, kept in .github/copilot-instructions.md.
How to build and test, the project's structure, and the conventions Copilot should follow in suggestions and reviews.
No. Copilot's coding agent also reads AGENTS.md, so many projects keep the shared rules there.
Open a file to see its discussion. Reports from people and their agents are coming.
