-
Couldn't load subscription status.
- Fork 5.4k
Clarify the location of md files for Copilot Chat customization within user profiles #8984
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.
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
base: main
Are you sure you want to change the base?
Clarify the location of md files for Copilot Chat customization within user profiles #8984
Conversation
Co-authored-by: CraftyCraftress <208521690+CraftyCraftress@users.noreply.github.com>
…t profile location Co-authored-by: CraftyCraftress <208521690+CraftyCraftress@users.noreply.github.com>
…phrasing Co-authored-by: CraftyCraftress <208521690+CraftyCraftress@users.noreply.github.com>
Co-authored-by: CraftyCraftress <208521690+CraftyCraftress@users.noreply.github.com>
Clarified storage locations for Default and additional profiles in user configurations.
|
@CraftyCraftress We don't include this information as we don't recommend users create those files directly in their user profile. The location of the files in the user profile might be subject to change. |
@ntrogh What is the suggested way to create & sync prompts/instructions across machines that are not repo/workspace specific? |
|
@CraftyCraftress When you create a prompt/instructions file (Chat: New Prompt File or Chat: New Instructions File), you can choose between workspace or user profile. For user-profile prompts or instructions, they are subject to settings sync, so will roam with you across machines.
|
@ntrogh Thanks! As a bit of feedback, it has taken longer than it should have for multiple people on my team to figure out how to manage instructions we want to share across machines. I think there's a couple reasons why:
In my opinion, it would be better for the documentation to just tell devs where the files are with the caveat that the location may change instead of trying to abstract it away and providing a sub-par experience that artificially introduces overhead. |
|
@CraftyCraftress Thanks for providing additional input. Reopening PR. |
|
@CraftyCraftress We've has some docs updates in the meantime that cause a merge conflict. Could you resolve? Otherwise LGTM! |

This change clarifies: