Skip to content

Update copilot instructions with baseline setup details #123064

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

Closed
stephentoub wants to merge 2 commits into from
Closed

Update copilot instructions with baseline setup details #123064

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
4958e13
Update copilot instructions with baseline setup details
stephentoub Jan 10, 2026
0dfe4a3
Clarify baseline setup requirements for builds and tests
stephentoub Jan 10, 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
2 changes: 2 additions & 0 deletions .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ You MUST make your best effort to ensure any code changes satisfy those criteria

If you make code changes, do not complete without checking the relevant code builds and relevant tests still pass after the last edits you make. Do not simply assume that your changes fix test failures you see, actually build and run those tests again to confirm. You can avoid building if you only change comments or files that do not affect builds and tests (e.g. README.md).

**In order to successfully build and run tests, you MUST first handle the baseline setup (see "1.2. Baseline Setup"), e.g. before you can build/test libraries, you must run `./build.sh clr+libs -rc release` at least once. This could take upwards of 10-20 minutes. You MUST wait for it to complete. You MUST not skip this step if you're making _any_ non-comment code changes.**
Copy link
Member

@jkotas jkotas Jan 10, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

./build.sh clr+libs -rc release

This is libraries workflow specific. Would it work better if this emphasis is in "1.2. Baseline Setup" that has the right command line to use?


You MUST follow all code-formatting and naming conventions defined in [`.editorconfig`](/.editorconfig).

In addition to the rules enforced by `.editorconfig`, you SHOULD:
Expand Down