sure
we-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
Steady30 mentions in 2 weeks
No other project uses it yet
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.
we-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
Steady30 mentions in 2 weeks
No other project uses it yet
microsoft/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
Steady12 mentions in 2 weeks
No other project uses it yet
dotnet/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
ArthurSonzogni/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
facebookresearch/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
No other project uses it yet
a-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
Steady3 mentions in 2 weeks
No other project uses it yet
facebook/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-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-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
Steady5 mentions in 2 weeks
No other project uses it yet
phpredis/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
shidenggui/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-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
roboflow/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
Steady3 mentions in 2 weeks
No other project uses it yet
crmne/spotifast/.github/copilot-instructions.md
visual approval from permission to assess code quality. Check that behavioural changes have focused tests and that user-visible settings, files, and network access are documented. For UI changes
1 project uses a version of this
microsoft/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
restsharp/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
Steady4 mentions in 2 weeks
No other project uses it yet
runtipi/runtipi/.github/copilot-instructions.md
commands to install dependencies, run scripts, and manage the project. - When asked to add tests, do not add e2e tests unless explicitly requested. Focus on unit tests and integration tests
Steady2 mentions in 2 weeks
No other project uses it yet
activeadmin/activeadmin/.github/copilot-instructions.md
Stack - **Backend**: Ruby on Rails (currently Rails ~> 8.1.0) - **Frontend**: JavaScript (ES6+), Tailwind CSS, Flowbite - **Testing**: RSpec (unit tests), Cucumber (feature tests), Capybara (integration tests) - **Build Tools**: Rollup (JavaScript bundling), cssbundling
No other project uses it yet
microsoft/fast/.github/copilot-instructions.md
This file describes the general instructions for working with the FAST monorepo, including repository structure, code style, tooling, and contribution guidelines.
No other project uses it yet
lepoco/wpfui/.github/copilot-instructions.md
library: dotnet build src/Wpf.Ui/Wpf.Ui.csproj Solution filters: - Wpf.Ui.Library.slnf - Library projects only - Wpf.Ui.Gallery.slnf - Gallery demo app Testing: - XUnit v3 for unit tests (tests/Wpf.Ui.UnitTests/) - AwesomeAssertions for assertions (FluentAssertions successor) - FlaUI for UI automation
Steady3 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.