This website uses cookies to ensure you get the best experience.
Learn more.
A monorepo has a common formatting convention and a separate rule used only for database migration files. How should the maintainer organize Copilot guidance in a supported client?
Published
- Duplicate every instruction in every source-code comment.
- Put the migration rules only in an unrelated developer's personal settings.
- Exclude migration files so that Copilot infers their conventions from filenames.
- Put common guidance in repository-wide instructions and migration rules in path-specific instruction files.
Comments — 0
Sign in to comment