How real projects brief GitHub Copilot, from .github/copilot-instructions.md.
MicrosoftCopilot instructionsmicrosoft/Tools-for-Health-Data-Anonymization/.github/copilot-instructions.md
detailed` ### Working with Azure Data Factory Components - Located in `*/AzureDataFactoryPipeline/` directories - PowerShell scripts for deployment in `*/scripts/` directories - Contains ARM templates for Azure resource deployment - Tests are often skipped (expected
Green-PTCopilot instructionsGreen-PT/honey-for-devs/.github/copilot-instructions.md
notification drive. Poll only external state the harness can't see (CI, deploy, remote queue). - **Short-circuit no-change ticks.** Cheap check first (hash/timestamp/`git rev-parse`); unchanged → one status
Alfanous-teamCopilot instructionsAlfanous-team/alfanous/.github/copilot-instructions.md
import/ # Data import tools │ └── tests/ # Test suite ├── store/ # Quranic data storage └── Makefile # Build and deployment commands ``` ## Development Workflow ### Setting Up the Development Environment 1. Install dependencies: ```bash pip install pyparsing
MicrosoftCopilot instructionsmicrosoft/SqlScriptDOM/.github/copilot-instructions.md
used by DacFx to build database projects, perform schema comparisons, and generate scripts for deployment. ## Key points (quick read) - Grammar files live in: `SqlScriptDom/Parser/TSql/` — each file corresponds
Microsoft AzureCopilot instructionsAzure/awesome-azd/.github/copilot-instructions.md
Standard structure with project name, use case, features, and architecture diagram - Step-by-step deployment and customization instructions - Getting started section with quick setup options (GitHub Codespaces, Dev Containers, local
Microsoft AzureCopilot instructionsAzure/git-ape/.github/copilot-instructions.md
Azure Deployment Standards ## Naming Conventions **⚠️ CRITICAL: Always use the `azure-naming-research` skill to lookup CAF abbreviations and Azure naming constraints before suggesting or validating resource names.** Use consistent
MicrosoftCopilot instructionsmicrosoft/GitHub-Copilot-for-Azure/.github/copilot-instructions.md
version.json # NBGV version rooted at 0.1 output/ # Build output (git-ignored) — stamped, ready to deploy / # Built plugin output hooks/ # Built shared hooks scripts/ # Dev tooling: token analysis, frontmatter/reference validators evals
EmpiricaAICopilot instructionsEmpiricaAI/empirica/.github/copilot-instructions.md
Chosen) ``` NOETIC (investigation) PRAXIC (action) -------------------- ----------------- Explore, hypothesize, Execute, write, search, read, question commit, deploy Completion = "learned Completion = "implemented enough to proceed?" enough to ship?" ``` You CHOOSE noetic vs praxic. CHECK
MicrosoftCopilot instructionsmicrosoft/AzureTRE/.github/copilot-instructions.md
want to build out Trusted Research Environments on Azure. It enables authorized users to deploy and configure secure workspaces and researcher tooling without a dependency on IT teams. Trusted Research
MicrosoftCopilot instructionsmicrosoft/MicroHack/03-Azure/01-04-AI/02_Inventory_Planning_Fabric/.github/copilot-instructions.md
front-end UI, but **all resource provisioning comes from `labautomation/deploy-lab.ps1`**. Without a working deployment script, no resources appear in the Azure portal — the platform is just a shiny front
thomast1906Copilot instructionsthomast1906/github-copilot-agent-skills/.github/copilot-instructions.md
Identities) - IaC (Bicep or Terraform) 5. **Document thoroughly** - Architecture diagrams - Service justifications - Cost estimates - Deployment strategy ## Naming Conventions Follow Cloud Adoption Framework naming standards: **Pattern:** `{resource-type}-{workload}-{environment}-{region
MicrosoftCopilot instructionsmicrosoft/mcp-dotnet-samples/.github/copilot-instructions.md
list:latest .` then `docker run -i --rm -p 8080:8080 todo-list:latest [--http]`. - Deploy (per sample): `azd auth login` then `azd up` inside sample folder, then read FQDN
CortexPrismCopilot instructionsCortexPrism/cortex/.github/copilot-instructions.md
active incidents" → `entity(kind="incident", action="list", query={"status": "investigating"})` - "create release" / "track release" / "deployment" → `entity(kind="release", action="create", body={"version": "1.4.0", "status": "planned", "environments": ["prod"], "git_ref": "..."})` - "list
Microsoft AzureCopilot instructionsAzure/gpt-rag-ingestion/.github/copilot-instructions.md
Removed` when applicable. On `develop`: - maintain exactly one `## [Unreleased]` section; - add every user-, operator-, deployment-, contract-, or release-relevant change under it; - do not create a future numbered release section
MicrosoftCopilot instructionsmicrosoft/Agents-for-net/.github/copilot-instructions.md
learn.microsoft.com/en-us/microsoft-365/agents-sdk/microsoft-authentication-library-configuration-options) - **ClientSecret/Certificate**: Works with dev tunnels for local debugging. - **Federated Credentials/Managed Identity**: Requires deployment to App Service or container (cannot use dev tunnel). ## Samples Samples are in `src/samples/`. Each
ECPayCopilot instructionsECPay/ECPay-API-Skill/.github/copilot-instructions.md
against.** Guides are sufficient for prototyping and initial development (parameter stability >95%). For production deployment or when API behavior doesn't match expectations, use `web_fetch` on references/ URLs
Azure-SamplesCopilot instructionsAzure-Samples/eShopLite/.github/copilot-instructions.md
scenario's `src/eShopAppHost` using `dotnet run` (or the provided VS Code task). - For Azure deployment, use `azd up` from the scenario root after `azd auth login`. - Local dev often requires
MicrosoftCopilot instructionsmicrosoft/simplechat/.github/copilot-instructions.md
confident the fix is robust and comprehensive. VERSIONING Application versioning remains in `application/single_app/config.py`. Deployer and CI/CD versioning lives separately in `deployers/version.txt`; when files under `deployers/` are modified, increment `deployers/version.txt
AiTerminalFoundationCopilot instructionsAiTerminalFoundation/ai-terminal/.github/copilot-instructions.md
tauri dev` before considering them complete - The application runs locally - no server-side deployment needed ## Common Tasks ### Adding a new Angular component: ```bash cd ai-terminal ng generate component component
MicrosoftCopilot instructionsmicrosoft/github-copilot-vibe-coding-workshop/docs/custom-instructions/containerization/copilot-instructions.md
other secret management solutions. - Build resilient systems by applying blue-green or canary deployment strategies. ## Specific Scenarios ### Docker and Docker Compose - Use multi-stage builds in Dockerfiles to optimize image
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.
