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.

Sign up for GitHub

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

Jump to bottom

vscode integration #568

Open
fridex opened this issue Nov 15, 2021 · 3 comments
Open

vscode integration #568

fridex opened this issue Nov 15, 2021 · 3 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/needs-information Indicates an issue needs more information in order to work on it.

Comments

@fridex
Copy link

fridex commented Nov 15, 2021

Is your feature request related to a problem? Please describe.

vscode is gaining popularity, especially considering in-browser development offered by GitHub. It might be interesting to add Thoth support to vscode. vscode already supports jupyter notebooks, it might be interesting to integrate there. Given vscode design, this might result in a new extension (not integrating support in jupyterlab-requirements that is an extension to jupyterlab).
@codificat
Copy link
Member

/kind feature
/triage needs-information

@sesheta sesheta added kind/feature Categorizes issue or PR as related to a new feature. triage/needs-information Indicates an issue needs more information in order to work on it. labels Nov 15, 2021
@sesheta
Copy link
Member

sesheta commented Feb 13, 2022

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@sesheta sesheta added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 13, 2022
@pacospace pacospace moved this from New to In Progress in jupyterlab-requirements Feb 14, 2022
@pacospace pacospace added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 14, 2022
@pacospace pacospace moved this from In Progress to To Do in jupyterlab-requirements Feb 17, 2022
@Gkrumbach07 Gkrumbach07 added the sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. label Aug 30, 2022
@Gkrumbach07
Copy link
Member

possible good intern project

@codificat codificat moved this to 🆕 New in Planning Board Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/feature Categorizes issue or PR as related to a new feature. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/user-experience Issues or PRs related to the User Experience of our Services, Tools, and Libraries. triage/needs-information Indicates an issue needs more information in order to work on it.
Projects
Planning Board
Status: 🆕 New
jupyterlab-requirements
Status: To Do
Milestone
No milestone
Development

No branches or pull requests
5 participants
@codificat @fridex @Gkrumbach07 @pacospace @sesheta