Instructions for the copilot-instructions.md file vs .github/instructions confusing #170581
Replies: 2 comments 1 reply
|
You can use both formats, and they serve slightly different purposes: .github/copilot-instructions.md -› repository-wide defaults. .github/instructions/*.instructions.md -›task-specific overrides. Copilot merges them at runtime, so the global file provides a baseline while the scoped files refine behavior for certain areas. Example: keep general guidance in copilot-instructions.md, and only add .instructions.md files when you need more granular control. |
|
ok, rereading the whole and chatting with an LLM, i realized the issue is that somehow it looks like either or (which would mean exclusivity), but in reality its just either, meaning both. I am wondering whether I am the only one confused, I think it might make sense to change the wording, maybe just "both" instead of "either" ? |
Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
Question
Copilot Feature Area
VS Code
Body
In the github docs about custom instructions, it reads:
while the VS Code instructions seem to suggest its ok to have both.
I am inclined to believe that since even the github instructions suggests that for some use cases only the "main file" works, the VS code instructions are probably right, but I also feel like I saw a few cases where the instructions seemed to be ignored, so maybe its not that ?
All reactions