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.
electronCopilot instructionselectron/electron/.github/copilot-instructions.md
lint:docs` ### Build Configuration - `BUILD.gn`: Main GN build config - `buildflags/buildflags.gni`: Feature flags (PDF viewer, extensions, spellchecker) - `build/args/`: Build argument profiles (`testing.gn`, `release.gn`, `all.gn`) - `DEPS`: Dependency versions and checkout paths - `chromium
No other project uses it yet
tesseract-ocrDeletes or force-pushesCopilot instructionstesseract-ocr/tesseract/.github/copilot-instructions.md
version tesseract --list-langs tesseract input.png output # OCR image, creates output.txt tesseract input.png output pdf # Create searchable PDF ``` Test files available in `test/testing/` (requires test submodule): - `phototest.tif` - English test image
1 project uses a version of this
MicrosoftCopilot instructionsmicrosoft/fluentui-system-icons/.github/copilot-instructions.md
deployment scripts (`deploy:android`, `deploy:ios`, `deploy:flutter`) which transform assets into vector drawables / PDF assets / Dart classes. ## Key Workflows (Local) - Install deps (root + packages): `corepack enable && yarn install --immutable
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.
