How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Microsoft AzureCopilot instructionsAzure/bicep/.github/copilot-instructions.md
under the MIT License.` - **Null-forgiving `!` operator is banned** in product code (allowed in tests) - **`Console.Write`/`Console.WriteLine` are banned**—use proper logging - Syntax trees and data structures are **immutable
bytebaseCopilot instructionsbytebase/dbhub/.github/copilot-instructions.md
email) VALUES ('John', 'john@example.com');` - `UPDATE users SET status = 'active' WHERE id = 1;` - `CREATE TABLE test_table (id INT PRIMARY KEY);` Use `--readonly` flag to restrict to read-only operations
MicrosoftCopilot instructionsmicrosoft/ebpf-for-windows/.github/copilot-instructions.md
Configuration=NativeOnlyDebug /p:Platform=x64 ebpf-for-windows.sln` | | Format code | `./scripts/format-code --staged` | | Run unit tests | `unit_tests.exe` (from `x64\Debug`) | | Run single test | `unit_tests.exe "test name"` | | List tests | `unit_tests.exe -l` | See [docs/GettingStarted.md](../docs/GettingStarted.md
TanStackCopilot instructionsTanStack/ai/.github/instructions/copilot-instructions.md
code, answering questions, or reviewing changes. Whenever you want to build the packages to test if they work you should run `pnpm run build` from the root of the repository
MicrosoftCopilot instructionsmicrosoft/Generative-AI-for-beginners-dotnet/.github/copilot-instructions.md
code formatting and style - Ensure all code builds with `dotnet build` and passes tests with `dotnet test` - Verify formatting with `dotnet format --verify-no-changes` if linting is enabled - **Build
MicrosoftCopilot instructionsmicrosoft/skills/.github/copilot-instructions.md
requested. - If you write 200 lines and it could be 50, rewrite it. **The test:** Would a senior engineer say this is overcomplicated? If yes, simplify. ### 3. Surgical Changes **Touch
MicrosoftCopilot instructionsmicrosoft/DirectXTK/.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/directxtktest/)
GitHubCopilot instructionsgithub/copilot-cli-for-beginners/.github/copilot-instructions.md
without explanation. - **Examples**: All code blocks and `copilot` commands must be copy-paste ready. Test them mentally before including. - **Naming**: Use kebab-case for session names, file names, and identifiers
MicrosoftCopilot instructionsmicrosoft/pg_durable/.github/copilot-instructions.md
happens here) | | [src/types.rs](../src/types.rs) | Core types: `Durofut`, `FunctionGraph`, `FunctionNode` | | [tests/e2e/sql/](../tests/e2e/sql/) | SQL-based E2E tests (numbered, run sequentially) | | [sql/pg_durable--0.1.1.sql](../sql/pg_durable--0.1.1.sql) | First version install SQL fixture (for upgrade testing) | ## Development Commands
MicrosoftCopilot instructionsmicrosoft/clarity/.github/copilot-instructions.md
Every byte matters. ## Build & Development Commands ### Installation **ALWAYS run `yarn install` before building or testing.** (~25s, peer dependency warnings are normal) ### Building ```bash yarn build # All packages (~45s, Lerna parallel
MicrosoftCopilot instructionsmicrosoft/litebox/.github/copilot-instructions.md
Build**: `cargo build` 3. **Lint**: `cargo clippy --all-targets --all-features` 4. **Test**: `cargo nextest run` - Full CI checks are defined in `.github/workflows/ci.yml`. ## Key Guidelines 1. Follow Rust best practices
MicrosoftCopilot instructionsmicrosoft/vscode-pull-request-github/.github/copilot-instructions.md
disabled in `tsconfig.base.json` (e.g., `strictNullChecks: false`), but new code should avoid unsafe patterns. - **Testing**: Place tests under `src/test`. Do not include test code in production files. - **Localization**: Use `%key%` syntax
MicrosoftCopilot instructionsmicrosoft/foundry-local/.github/copilot-instructions.md
glob auto-attachment). Keep facts concise and actionable. ## File Hygiene - **Temporary and scratch files** (test logs, coverage reports, build artifacts, diagnostic outputs) must be created inside the build output directory
Microsoft AzureCopilot instructionsAzure/azure-sdk-for-java/.github/copilot-instructions.md
Behavior - Always ensure your solutions prioritize clarity, maintainability, and testability. - Never suggest re-recording tests as a fix to an issue - NEVER turn off any Checkstyle or SpotBugs rules
KuddevCopilot instructionsKuddev/nebula/.github/copilot-instructions.md
than inventing a second rule set. Check ownership, dependency direction, cancellation/lifetime, persistence compatibility, and tests appropriate to the change. Consult `docs/internationalization.md` for UI text and `packaging/AGENTS.md` for release changes. Verify
MicrosoftCopilot instructionsmicrosoft/CsWin32/.github/copilot-instructions.md
this repository ## High level guidance * Review the `CONTRIBUTING.md` file for instructions to build and test the software. * Set the `NBGV_GitEngine` environment variable to `Disabled` before running any `dotnet
MicrosoftCopilot instructionsmicrosoft/Olive/.github/copilot-instructions.md
requirements-dev.txt` -- takes 20 seconds. - Initialize linting: `lintrunner init` -- takes 15 seconds. ### Build and Test Commands - Lint code: `lintrunner` -- takes 1-2 seconds for single files, 5+ seconds for entire codebase
llmsresearchCopilot instructionsllmsresearch/paperbanana/.github/copilot-instructions.md
Copilot Instructions for PaperBanana ## Build & Test ```bash # Install for development pip install -e ".[dev,openai,google]" # Run full test suite pytest tests/ -v # Run a single test file pytest tests/test_pipeline/test_types.py
MicrosoftCopilot instructionsmicrosoft/pxt/.github/copilot-instructions.md
arrow functions for callbacks and short functions - Include error handling for async operations ## Testing Requirements - Write unit tests for new functionality - Include accessibility tests for UI components - Test simulator features
AWSCopilot instructionsaws/sagemaker-python-sdk/.github/copilot-instructions.md
backward compatible with v2. Generate v3 patterns in all example code, docstrings, tests, and docs unless v2 is explicitly in scope. - **SDK-first.** Use the SageMaker Python
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.
