How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
bunkerityCopilot instructionsbunkerity/bunkerweb/.github/copilot-instructions.md
integrations) - `docs/`: Documentation, guides, and assets - `examples/`: Real-world configuration and deployment examples - `tests/`: Test scripts and scenarios - `misc/`: Utilities, scripts, and ASCII art ## Developer Workflows - **Build/Run**: See `docs/quickstart-guide.md
No other project uses it yet
mRemoteNGCopilot instructionsmRemoteNG/mRemoteNG/.github/copilot-instructions.md
Windows (net10.0-windows10.0.26100.0) - **UI Framework**: Windows Forms with WPF support - **Target Platforms**: x64 and ARM64 - **Testing Framework**: NUnit with NSubstitute for mocking - **Build System**: MSBuild with .NET SDK-style projects ## Building
No other project uses it yet
omnigent-aiCopilot instructionsomnigent-ai/omnigent/.github/copilot-instructions.md
Copilot Code Review Instructions ## E2E Test Requirement Every pull request that introduces a new feature **must** include at least one end-to-end (e2e) test covering the happy-path behaviour
HashiCorpCopilot instructionshashicorp/terraform-provider-aws/.github/copilot-instructions.md
Tags (schema attrs, wiring, annotation) | `instructions/tags.instructions.md` | `internal/service/**/*.go` | | Generated code | `instructions/generated.instructions.md` | `internal/service/**/*_gen.go` | | Acceptance test basics | `instructions/acceptance-tests.instructions.md` | `internal/service/**/*_test.go` | | Test helpers (Exists/Destroy, list/data source/unit tests) | `instructions/acceptance-tests-helpers.instructions.md` | `internal/service/**/*_test.go` | | User-facing
No other project uses it yet
openvinotoolkitCopilot instructionsopenvinotoolkit/openvino/.github/copilot-instructions.md
maintainer review requests are defined separately in `.github/CODEOWNERS`. ## Repository practices - Inspect the relevant implementation, tests, build files, and documentation before editing. - Keep changes focused on the requested behavior. Preserve unrelated
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/fluentui-system-icons/.github/copilot-instructions.md
affected builds. If React pipelines failed you will probably need to update metadata.json and test snapshot to reflect new assets addition. - Run `yarn nx run react-icons:build` to regenerate
No other project uses it yet
dotnetCopilot instructionsdotnet/orleans/.github/copilot-instructions.md
directory instructions for implementation principles and repository workflow. For code review, use `.github/skills/code-review/SKILL.md`. ## Build, test, and style commands * The repo builds with the .NET SDK from `global.json` (`10.0.400`, roll-forward
No other project uses it yet
ArthurSonzogniDeletes or force-pushesCopilot instructionsArthurSonzogni/FTXUI/.github/copilot-instructions.md
time: ~70 seconds. NEVER CANCEL. Set timeout to 180+ seconds. # Build with examples and tests cmake -S . -B build -DCMAKE_BUILD_TYPE=Release -DFTXUI_BUILD_EXAMPLES=ON -DFTXUI_BUILD_TESTS
No other project uses it yet
we-promiseCopilot instructionswe-promise/sure/.github/copilot-instructions.md
linked there when their subjects apply to the task, including the development checks, architecture, testing, UI, API and provider guides
No other project uses it yet
MetaCopilot instructionsfacebookresearch/hydra/.github/copilot-instructions.md
against the contributor guidelines and call out only actionable gaps, especially: - missing or insufficient tests for code changes; - missing documentation updates for API or behavior changes; - missing news fragments
a-hCopilot instructionsa-h/templ/.github/copilot-instructions.md
Behaviour * Always run `go fmt` after making changes to Go code. * Always run unit tests after making changes to Go code. ## Environment setup * Ensure that the user has direnv installed
Steady6 mentions in 2 weeks
No other project uses it yet
facebookCopilot instructionsfacebook/stylex/.github/copilot-instructions.md
Flag if any CI check is failing and the PR does not acknowledge it. - **Tests**: New babel-plugin features or bug fixes must include tests. Prefer `toMatchInlineSnapshot()` for all assertion
No other project uses it yet
vmware-tanzuCopilot instructionsvmware-tanzu/velero/.github/copilot-instructions.md
coding guidelines - Follow the existing code style of the file being edited. - Add unit tests for new exported functions in `pkg/`. - Do not commit secrets, credentials, or API tokens. - Keep
No other project uses it yet
OpenCTI-PlatformDeletes or force-pushesCopilot instructionsOpenCTI-Platform/opencti/.github/copilot-instructions.md
everything yarn build # without Python virtualenv yarn build:venv # with Python virtualenv # Run all tests yarn test # without Python virtualenv yarn test:venv # with Python virtualenv # Lint everything yarn lint
phpredisCopilot instructionsphpredis/phpredis/.github/copilot-instructions.md
with PhpRedis practices. ## What this project is PhpRedis is a PHP extension (C + PHP test suites) for Redis/Valkey. Project homepage: https://github.com/phpredis/phpredis ## Golden rules for Copilot 1. **Never commit
No other project uses it yet
shidengguiCopilot instructionsshidenggui/easytrader/.github/copilot-instructions.md
newer code like `miniqmt/`). Match the style of the surrounding code. ## Build and Test ```bash # Install pipenv install # Run tests (only xq_follower and xqtrader tests are runnable without Windows
No other project uses it yet
go-swaggerCopilot instructionsgo-swagger/go-swagger/.github/copilot-instructions.md
with explicit disables). - Every `//nolint` directive **must** have an inline comment explaining why. - Tests: `go test ./...` (single module). CI runs on `{ubuntu, macos, windows} x {stable, oldstable}` with `-race`. - Test
No other project uses it yet
MicrosoftCopilot instructionsmicrosoft/vscode-copilot-chat/.github/copilot-instructions.md
proposed APIs for chat, language models, and editing - **ESBuild**: Bundling and compilation - **Vitest**: Unit testing framework - **Python**: For notebooks integration and ML evaluation scripts ## Validating changes You MUST check compilation
roboflowCopilot instructionsroboflow/rf-detr/.github/copilot-instructions.md
Copilot Instructions > [!NOTE] > > This document is GitHub Copilot-specific guidance. For canonical contribution guidelines (test-driven development, code quality, docstrings, etc.), see [CONTRIBUTING.md](CONTRIBUTING.md). For detailed agent-specific context
restsharpCopilot instructionsrestsharp/RestSharp/.github/copilot-instructions.md
Main library - `src/RestSharp.Serializers.*/` - Serializer extensions (NewtonsoftJson, Xml, CsvHelper) - `gen/SourceGenerator/` - Incremental source generators - `test/RestSharp.Tests/` - Unit tests - `test/RestSharp.Tests.Integrated/` - Integration tests (WireMock) - `test/RestSharp.Tests.Serializers.*/` - Serializer-specific tests - `benchmarks/RestSharp.Benchmarks/` - Performance tests ## Build and Test Commands
Steady28 mentions in 2 weeks
No other project uses it yet
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.
