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
Assume I have a huge monorepository.
We're talking all kinds of projects, rust, dotnet, typescript etc.
say 50+ unique, projects. Each require their own copilot-instruction(s) (probably).
My understanding is using APM is repository wide, and for example skills / plugins etc are installed in root of git repository.
My question is:
Can install location in repo be customized on a per package basis (preferably multiple paths..)?
Can github copilot adjust to use the correct packages, and ignore the repo-root? This might connect to whichever "workspace" the user has in their IDE. For example, a user may have a .Net solution open in visual studio / or visual studio code, but we really dont want to bloat context with skills and other auto-loaded instructions about a folder with rust projects.
The primary concern is a to huge instructions file initially, and scope the conversations / agentic AI to only use the context in "current workspace folder", not current git repository root.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi.
Assume I have a huge monorepository.
We're talking all kinds of projects, rust, dotnet, typescript etc.
say 50+ unique, projects. Each require their own copilot-instruction(s) (probably).
My understanding is using APM is repository wide, and for example skills / plugins etc are installed in root of git repository.
My question is:
The primary concern is a to huge instructions file initially, and scope the conversations / agentic AI to only use the context in "current workspace folder", not current git repository root.
I'ev read https://github.com/orgs/community/discussions/179916
regarding github copilot spaces, but spaces is SEPERATE from code. Spaces is not an option.
Beta Was this translation helpful? Give feedback.
All reactions