Skip to content

Add guidance for searching multi-line function call chains in Copilot instructions #3138

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from
+2 −0
Open

Add guidance for searching multi-line function call chains in Copilot instructions #3138

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2c5e8cc
Initial plan
Copilot Oct 7, 2025
e25e19a
Add guidance for searching multi-line function call chains in Rust
Copilot Oct 7, 2025
ce3e1c6
Condense searching guidance into single bullet point
Copilot Oct 7, 2025
eac7aab
Add rustfmt to cspell.json word list
Copilot Oct 7, 2025
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
1 change: 1 addition & 0 deletions .github/copilot-instructions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,6 +37,7 @@ Use these instructions for test generation as well.
- If you have trouble generating safe, efficient, maintainable, and lint-free code, insert a `TODO` comment describing what should happen.
- All imported types, constants, functions, modules, and macros should be imported explicitly. Never import `*`.
- Do not modify generated code, found in `generated` subdirectories. These files are generated by external tools and should not be edited manually.
- When searching for function call chains in Rust code, be aware that rustfmt often formats method chains across multiple lines like `obj\n .foo()\n .bar()`. Use multi-line search patterns (e.g., `rg` with `-U` flag) or search for individual method names rather than complete call chains.

## Test Generation

Expand Down
Loading