Skip to content
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

Enable "Trusted Workspaces". #15525

Closed
ericsnowcurrently opened this issue Mar 1, 2021 · 0 comments · Fixed by #15521
Closed

Enable "Trusted Workspaces". #15525

ericsnowcurrently opened this issue Mar 1, 2021 · 0 comments · Fixed by #15521
Assignees
Labels
area-internal Label for non-user facing issues debt Covers everything internal: CI, testing, refactoring of the codebase, etc.

Comments

@ericsnowcurrently
Copy link
Member

(see microsoft/vscode-python-internalbacklog#37)

We need to add support for the upcoming "Trusted Workspaces" feature in VS Code.

@ericsnowcurrently ericsnowcurrently added needs PR debt Covers everything internal: CI, testing, refactoring of the codebase, etc. area-internal Label for non-user facing issues labels Mar 1, 2021
@ericsnowcurrently ericsnowcurrently self-assigned this Mar 1, 2021
ericsnowcurrently added a commit that referenced this issue Mar 3, 2021
(closes #15525)

This change enables the new "Trusted Workspaces" feature of VS Code (see microsoft/vscode#106488) for the extension.  For now a user must put `"workspace.trustEnabled": true` in their settings.json to trigger the functionality (and it only works on VS Code insiders).
@ghost ghost removed the needs PR label Mar 3, 2021
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 2, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-internal Label for non-user facing issues debt Covers everything internal: CI, testing, refactoring of the codebase, etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant