You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Status of implementing features provided in the vscode copilot, like custom instructions? #101
Vscode is maintained by Microsoft, and so is this. It seems like the copilot features in vscode are getting a lot of attention, but this Eclipse plugin is barely keeping up. For instance, I realize now that the ".github/copilot-instructions.md" that we create in our enterprise is only used by vscode copilot. This Eclipse plugin doesn't use it by default. There are also additional more discrete instructions files, but again, this is only used in vscode. What is the plan for achieving parity with the vscode features?
David M. Karr (@davidmichaelkarr): I think the .github/copilot-instructions.md already loaded into the context automatically, see the merged PR #136
Sheng Chen (@jdneo): can you confirm that? What is not clear to me where the .github\copilot-instructions.md file should be located? Directly under the git root (<gitroot>/.github/copilot-instructions.md) or in a project that is loaded into the workspace (<gitroot>/<projectThatIsLoadedIntoTheWorkspace>/.github/copilot-instructions.md) ?
Currently both git root and IProject's root will take effect. But I strongly recommend to put it under git root, which is the common location where .github locates.
Sheng Chen (@jdneo): thanks for clarifying this. However Copilot says that it does not have access to <gitroot>/.github/copilot-instructions.md if it’s not imported into the workspace. So putting the file under <gitroot>/.github/copilot-instructions.md has no effect.
Would it be possible to make copilot aware of the <gitroot>/.github/copilot-instructions.md files independent of whether it is imported into the workspace or not?
I have provided an implementation to detect the instructions form the git repo even if the root is not imported into the workspace a month ago. Tamas has tested it from a users perspective. What is missing is a review from a maintainer. I have just updated the branch to be recent. What is missing is a review of an maintainer. Any chance to have a look at #466 ?
Activity
ethanyhou commentedon Mar 12, 2026
cc Hang Wang (@hangwan97)
tamasmiklossy commentedon Jul 2, 2026
David M. Karr (@davidmichaelkarr): I think the
.github/copilot-instructions.mdalready loaded into the context automatically, see the merged PR #136Sheng Chen (@jdneo): can you confirm that? What is not clear to me where the
.github\copilot-instructions.mdfile should be located? Directly under the git root (<gitroot>/.github/copilot-instructions.md) or in a project that is loaded into the workspace (<gitroot>/<projectThatIsLoadedIntoTheWorkspace>/.github/copilot-instructions.md) ?CC: Andrey Loskutov (@iloveeclipse)
jdneo commentedon Jul 3, 2026
Currently both git root and IProject's root will take effect. But I strongly recommend to put it under git root, which is the common location where
.githublocates.tamasmiklossy commentedon Jul 30, 2026
Sheng Chen (@jdneo): thanks for clarifying this. However Copilot says that it does not have access to
<gitroot>/.github/copilot-instructions.mdif it’s not imported into the workspace. So putting the file under<gitroot>/.github/copilot-instructions.mdhas no effect.Or do I misunderstand it ?
jdneo commentedon Jul 30, 2026
Ah yes, if you only partially import a sub module into the workspace, then the real root is invisible because it is not in workspace.
tamasmiklossy commentedon Jul 30, 2026
Would it be possible to make copilot aware of the
<gitroot>/.github/copilot-instructions.mdfiles independent of whether it is imported into the workspace or not?ArneDeutsch commentedon Sep 29, 2026
I have implemented a discovery mechanism of custom instructions/skills/agents etc. that works similar as in VS code. For details see the PR: #466
ArneDeutsch commentedon Oct 29, 2026
I have provided an implementation to detect the instructions form the git repo even if the root is not imported into the workspace a month ago. Tamas has tested it from a users perspective. What is missing is a review from a maintainer. I have just updated the branch to be recent. What is missing is a review of an maintainer. Any chance to have a look at #466 ?