Skip to content

docs: adds additional copilot instructions for commit, tdd, linting, etc... #9632

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
baywet merged 2 commits into from
Feb 6, 2026
Merged

docs: adds additional copilot instructions for commit, tdd, linting, etc... #9632

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7eb79a6
docs: adds additional copilot instructions for commit, tdd, linting, …
baywet Feb 6, 2026
5ff50a1
Update .github/copilot-instructions.md
baywet Feb 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -115,6 +115,16 @@ TypeSpec is a language for defining cloud service APIs and shapes. This monorepo
- If TypeScript compilation fails, check that compiler built first: `pnpm -r --filter "@typespec/compiler" build`
- For VS Code extension development, ensure you have the workspace open at the repository root

## Commit instructions

- Always run the linting and the formatting commands before any commit.
- Follow conventional commits.

## Pull Request instructions

- When the work is done, run `@npx @chronus/chronus add` to add a changelog entry. Make sure to select the correct type of change (fix, feat, docs, etc.) and provide a clear description based on the initial issue description. Also prefix the description with the component name (e.g. if the component is the importer `importer - `).
- Always start by defining additional unit tests/updating existing unit tests to fulfill the requirements first. Then make changes to the code accordingly. If you are following the TDD (Test Driven Development) approach, make sure to run the tests and see them fail before implementing the code changes.

## Available Task Instructions

- [Testserver Generation](./prompts/testserver-generation.md): Instructions for generating TypeSpec HTTP spec test servers
Expand Down