muxy
muxy-app/muxy/.github/copilot-instructions.md
applicable repository standards using one evidence-gathering pass. Do not build, lint, run tests, or modify code during a review unless the user explicitly asks. For changes of at most
How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
muxy-app/muxy/.github/copilot-instructions.md
applicable repository standards using one evidence-gathering pass. Do not build, lint, run tests, or modify code during a review unless the user explicitly asks. For changes of at most
microsoft/DirectXTex/.github/copilot-instructions.md
marked `noexcept`, use `std::nothrow` for memory allocation, and should not throw exceptions. - **Testing**: Unit tests for this project are implemented in this repository [Test Suite](https://github.com/walbourn/directxtextest/)
Azure/AKS/.github/copilot-instructions.md
Title**: Follows conventional commit format - **Description**: What changed and why, link to related issues - **Testing**: Describe validation (e.g., "npm run build passed") - **Screenshots**: Include for UI changes --- ### Azure/Kubernetes Best Practices
Lumiwealth/lumibot/.github/copilot-instructions.md
Instructions for Copilot Important: remember to add unit tests for any new functionality you add. This is mission critical code, so we need to ensure that it works as expected
microsoft/intelligent-terminal/.github/copilot-instructions.md
find it at `C:\Program Files\Microsoft Visual Studio\2022\ \Common7\IDE\`. ## Test Tests use **TAEF** (Test Authoring and Execution Framework), not Visual Studio Test. Run from a razzle environment
microsoft/maker.js/.github/copilot-instructions.md
being committed with `git status` or `git diff --cached` 2. Ensure only source code, tests, and documentation are included 3. Check that no build artifacts or lockfiles are being staged
Azure/azure-functions-host/.github/copilot-instructions.md
null checks when the type system says a value cannot be null. ### Testing * Do not emit "Act", "Arrange" or "Assert" comments. * Use Moq for mocking in tests. * Copy existing style
microsoft/msticpy/.github/copilot-instructions.md
msticpy` (in `msticpy/`) - **Import pattern**: `import msticpy as mp` - **Source**: `msticpy/` contains implementation modules - **Tests**: `tests/` with pytest markers: `unit`, `integration`, `slow` - **Tools**: `tools/` supplementary tools not core
microsoft/snmalloc/.github/copilot-instructions.md
Before beginning implementation of any plan, verify that the current checkout builds and passes tests. Run the build and test suite (per `.github/skills/building_and_testing.md`) and record the results. If the baseline
microsoft/openvmm/.github/copilot-instructions.md
does not apply to untrusted input — use error handling at trust boundaries, not assertions.) ## Testing Run tests with cargo-nextest using the `agent` profile, which suppresses output for passing tests
microsoft/azure-pipelines-agent/.github/copilot-instructions.md
from the `src/` directory: #### Linux/macOS ```bash ./dev.sh {command} [target_framework] [build_config] [runtime_id] [test_filters] ``` #### Windows ```cmd dev {command} [target_framework] [build_config] [runtime_id] [test_filters] ``` ### Available Commands
Azure/azure-sdk-for-go/.github/copilot-instructions.md
agents. - Documents related to setting up your machine for development, deprecating libraries, and writing tests can be found here: https://github.com/Azure/azure-sdk-for-go/tree/main/documentation. - To contact a member of the Go team
microsoft/DirectXMath/.github/copilot-instructions.md
marked `noexcept`. A few functions have `bool` results to indicate success or failure. - **Testing**: Unit tests for this project are implemented in a separate repository [Test Suite](https://github.com/walbourn/directxmathtest/)
microsoft/DirectXTK12/.github/copilot-instructions.md
marked `noexcept`, use `std::nothrow` for memory allocation, and should not throw exceptions. - **Testing**: Unit tests for this project are implemented in this repository [Test Suite](https://github.com/walbourn/directxtk12test/)
relaticle/relaticle/.github/copilot-instructions.md
enforces: PHPStan level 7, Pint formatting, Rector, 99.9% type coverage, full test suite. CI does **not** enforce: code coverage percentage, mutation testing, or required reviewer count. ## Tenant Isolation: Flag These
microsoft/vscode-cmake-tools/.github/copilot-instructions.md
You are an expert contributor to microsoft/vscode-cmake-tools, a TypeScript VS Code extension targeting Windows, macOS, and Linux. You are deeply familiar with CMake, CMake Presets, CTest, CPack, generator types (Ninja, Ninja Multi-Config, Visual Studio, Unix Makefiles), kit/toolchain selection, the VS Code extension API, and this repo's architecture. Match existing patterns precisely and always prefer tracing the canonical data flow over guessing or grepping.
github/codeql-action/.github/copilot-instructions.md
TypeScript projects. - The main TypeScript codebase is in the `src` directory, with accompanying unit tests in `.test.ts` files in the same directory. - The main codebase is compiled to bundled JavaScript
microsoft/OpenAPI.NET/.github/copilot-instructions.md
fixes a bug nor adds a feature - **perf**: A code change that improves performance - **test**: Adding missing tests or correcting existing tests - **build**: Changes that affect the build system
microsoft/vscode-jupyter/.github/copilot-instructions.md
changes to ensure proper code formatting ## Development Flow - **Compile**: `npm run compile` (required before testing code changes) - **Run all unit tests**: `npm run test:unittests` - **Run specific unit tests
Azure/data-api-builder/.github/copilot-instructions.md
builder/ ├── src/ │ ├── Auth/ # Authentication logic │ ├── Cli/ # Command-line interface (dab CLI) │ ├── Cli.Tests/ # CLI tests │ ├── Config/ # Configuration handling │ ├── Core/ # Core engine components │ ├── Service/ # Main DAB service/runtime │ ├── Service.GraphQLBuilder/ # GraphQL schema builder │ ├── Service.Tests
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.