-
Notifications
You must be signed in to change notification settings - Fork 164
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
[Usability] Make it easier to use VS Code Desktop #453
Comments
peterschmidt85
added a commit
that referenced
this issue
Jun 4, 2023
… replace it with something more coherent) #448 - [Internals] Forbid running providers via the CLI without YAML #452 - [Usability] Allow to place YAML files anywhere and define workflows on the top level and use path instead of a workflow name #417 - [Usability] Make it easier to use multiple resource profiles #447 - [Usability] Make it easier to use VS Code Desktop #453
12 tasks
Here's a relevant link that in theory may help pre-install VS Code and extensions: microsoft/vscode-remote-release#1718 |
peterschmidt85
added a commit
that referenced
this issue
Jun 6, 2023
… replace it with something more coherent) #448 - [Internals] Forbid running providers via the CLI without YAML #452 - [Usability] Allow to place YAML files anywhere and define workflows on the top level and use path instead of a workflow name #417 - [Usability] Make it easier to use multiple resource profiles #447 - [Usability] Make it easier to use VS Code Desktop #453
peterschmidt85
added a commit
that referenced
this issue
Jun 6, 2023
- [Usability] Hide the low-level provider abstraction from YAML (e.g. replace it with something more coherent) #448 - [Internals] Forbid running providers via the CLI without YAML #452 - [Usability] Allow to place YAML files anywhere and define workflows on the top level and use path instead of a workflow name #417 - [Usability] Make it easier to use multiple resource profiles #447 - [Usability] Make it easier to use VS Code Desktop #453 - Fixes after merging with `master`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Scope:
ipykernel
The text was updated successfully, but these errors were encountered: