mirror of
https://github.com/github/awesome-copilot.git
synced 2026-07-14 10:01:06 +00:00
Komal Vardhan Lolugu
0fa87ab383
* Refresh 6 stale instruction files flagged in #2133 Targeted refresh: - blazor: C# 13 to C# 14. Drop the Visual Studio Enterprise mandate so contributors on VS Code or Rider aren't blocked by a paid SKU. Swap VS-only profiling for dotnet-trace and dotnet-counters. - copilot-thought-logging: narrow applyTo from '**' to '**/Copilot-Processing.md'. Replace 9 Windows backslash paths with POSIX './Copilot-Processing.md' so the workflow works on macOS and Linux. - genaiscript: drop the "avoid exception handlers or error checking" line. Replace it with: handle errors at I/O and external API boundaries, let unexpected exceptions surface. - memory-bank: add the required 'description' frontmatter field (was a validation failure). Narrow applyTo from '**' to 'memory-bank/**'. Add an opt-in note so contributors know auxiliary files land in the workspace root. Minor modernization: - azure-functions-typescript: Node.js v20 to v22 LTS. - localization: relative '../../issues' disclaimer link to absolute https://github.com/github/awesome-copilot/issues so it resolves regardless of the localized doc's path. docs/README.instructions.md regenerated by 'npm run build' to pick up the new memory-bank description. * revert applyTo narrow on copilot-thought-logging (#2133 review) aaronpowell flagged that narrowing applyTo from '**' to '**/Copilot-Processing.md' inverts the instruction. The instruction tells Copilot to CREATE Copilot-Processing.md when handling any user request, so it must apply globally, not only when that file is already open. Restore applyTo to '**'. Keep the POSIX path fixes (backslash to './Copilot-Processing.md') and the other 5 file fixes in this PR unchanged. --------- Co-authored-by: Aaron Powell <me@aaron-powell.com>
817 B
817 B
description, applyTo
| description | applyTo |
|---|---|
| TypeScript patterns for Azure Functions | **/*.ts, **/*.js, **/*.json |
Guidance for Code Generation
- Generate modern TypeScript code for Node.js
- Use
async/awaitfor asynchronous code - Whenever possible, use Node.js v22 LTS built-in modules instead of external packages
- Always use Node.js async functions, like
node:fs/promisesinstead offsto avoid blocking the event loop - Ask before adding any extra dependencies to the project
- The API is built using Azure Functions using
@azure/functions@4package. - Each endpoint should have its own function file, and use the following naming convention:
src/functions/<resource-name>-<http-verb>.ts - When making changes to the API, make sure to update the OpenAPI schema (if it exists) and
README.mdfile accordingly.