How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/clrmd/.github/copilot-instructions.md
internals (heap, types, threads, GC roots, exceptions) similar to SOS debugging extensions. ## Build & Test ```bash # Build the solution (does NOT build test targets or generate dumps): dotnet build Microsoft.Diagnostics.Runtime.sln
mongodb-jsCopilot instructionsmongodb-js/mongodb-mcp-server/.github/copilot-instructions.md
packages/types`: Shared types (`UserConfig`, `TransportRequestContext`, `ToolCategory`, `OperationType`, `ServerMetadata`, `McpSession`, …). - `packages/ui`: MCP UI resources (`UIRegistry`). - Test packages: `packages/integration-tests` (start the server and interact with it), `packages/accuracy-tests` (accuracy tests that use different
MicrosoftCopilot instructionsmicrosoft/mssql-jdbc/.github/copilot-instructions.md
Driver source**: All source code in `src/main/java/com/microsoft/sqlserver/jdbc/`. - **Error resources**: Localized error messages in `SQLServerResource.java`. - **Tests**: Located in `src/test/java/com/microsoft/sqlserver/jdbc/`. - **Unit Tests**: Many tests in `src/test/java/com/microsoft/sqlserver/jdbc/unit/` are isolated, but this tree
MicrosoftCopilot instructionsmicrosoft/onnxruntime-genai/.github/copilot-instructions.md
platform Python build script (preferred) python build.py --config Release --use_cuda --build_java --enable_tests # Platform-specific scripts build.bat # Windows batch build.sh # Linux/Mac shell ``` ### Key Build Options (cmake/options.cmake) - `USE_CUDA/USE_DML
MicrosoftCopilot instructionsmicrosoft/shell-intune-samples/.github/copilot-instructions.md
These are **sample** scripts for educating Intune administrators; they are run in non-production / test environments only. Keep changes focused, idempotent, and consistent with the existing `##` banner plus Microsoft copyright
openops-cloudCopilot instructionsopenops-cloud/openops/.github/copilot-instructions.md
Request Review Guidelines Review the current pull request diff for security, code quality/readability, performance, test coverage, and user impact. Only comment when there is a concrete issue introduced or affected
MicrosoftCopilot instructionsmicrosoft/bf-tree/.github/copilot-instructions.md
Copilot Instructions for bf-tree ## Build, Test, and Lint ```bash # Build (release mode recommended — debug builds are large) cargo build --release # Run all unit tests cargo test # Run a single
MicrosoftCopilot instructionsmicrosoft/testfx/.github/copilot-instructions.md
GitHub Copilot Instructions This is a .NET based repository that contains the MSTest testing framework and Microsoft.Testing.Platform (aka MTP) testing platform. Please follow these guidelines when contributing: ## Repository layout
MicrosoftCopilot instructionsmicrosoft/BuildXL/.github/copilot-instructions.md
outputs. Unobserved file accesses can fail a build or make it uncacheable. ## Building and testing Run builds from the repository root. On Windows, invoke the batch file through
MicrosoftCopilot instructionsmicrosoft/qdk/.github/copilot-instructions.md
frontend - **qsc_rca/**: Resource counting and analysis - **qsc_rir/**: Runtime Intermediate Representation - **fuzz/**: Fuzz testing infrastructure for the compiler - **language_service/**: Q# language service for editor features - **noisy_simulator/**: Simulator
MicrosoftCopilot instructionsmicrosoft/DevSkim/.github/copilot-instructions.md
avoid writing an entry for a real change. ## Building and Testing ### VS Code Plugin (TypeScript) **Location**: `./DevSkim-VSCode-Plugin/` **Setup**: ```bash cd DevSkim-VSCode-Plugin npm run setup # Install dependencies and build
NVIDIACopilot instructionsNVIDIA/cudf-spark/.github/copilot-instructions.md
locks without ordering - [ ] H3: Fallback gaps — new replacement rule without a fallback declaration or test - [ ] H4: Test quality — no GPU execution verification, hardcoded sleeps, unseeded random data; GPU resource cleanup
MicrosoftCopilot instructionsmicrosoft/vstest/.github/copilot-instructions.md
This is a .NET based repository that contains the VSTest test platform. Please follow these guidelines when contributing: ## Code Standards You MUST follow all code-formatting and naming conventions defined
Microsoft AzureCopilot instructionsAzure/azure-service-operator/.github/copilot-instructions.md
install-dependencies script to complete** - It installs necessary tools and dependencies for builds and tests. Interrupting it can lead to incomplete setup, build failures, and use of incompatible tool versions
Microsoft AzureCopilot instructionsAzure/azure-service-operator/.github/instructions/copilot-instructions.md
format-code ``` 2. **Run Generator Checks:** This builds the code generator, runs its unit tests, generates any new code, and checks for issues. ```bash task generator:quick-checks
MicrosoftCopilot instructionsmicrosoft/fabric-toolbox/tools/fabric-assessment-tool/.github/copilot-instructions.md
Copilot Instructions for Fabric Assessment Tool ## Build, Test & Lint ```bash # Install in development mode pip install -e . # Run all tests with coverage tox run -e py312 # or py310, py311
AWSCopilot instructionsawslabs/agent-plugins/.github/copilot-instructions.md
gitleaks for secret detection 2. **Documentation**: Comprehensive guides including DEVELOPMENT_GUIDE.md, CONTRIBUTING.md, TROUBLESHOOTING.md 3. **Testing**: Follow existing test patterns in the codebase 4. **Formatting**: Use dprint for code formatting consistency
MicrosoftCopilot instructionsmicrosoft/OpenAIWorkshop/.github/copilot-instructions.md
your changes when relevant - Ask yourself: “Would a staff engineer approve this?” - Run tests, check logs, demonstrate correctness ### 5. Demand Elegance (Balanced) - For non-trivial changes: pause
ChiR24Copilot instructionsChiR24/Unreal_mcp/.github/copilot-instructions.md
rely on the closer `AGENTS.md` files for area-specific detail under `src/tools/`, `src/tools/handlers/`, `src/automation/`, `tests/`, and `plugins/McpAutomationBridge/`. ## Critical constraints - Keep stdout JSON-only. Runtime logs must go through the project
pocketpawCopilot instructionspocketpaw/pocketpaw/.github/copilot-instructions.md
asyncio.to_thread()` for unavoidable blocking calls (e.g. a sync-only third-party SDK). - Tests use `pytest-asyncio` in **`asyncio_mode = "auto"`** — no `@pytest.mark.asyncio` decorator needed. - Never call `asyncio.run()` inside library
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.
