You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/commands.json
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -261,7 +261,7 @@
261
261
"action": "close",
262
262
"reason": "not_planned",
263
263
"addLabel": "*caused-by-extension",
264
-
"comment": "It looks like this is caused by the Jupyter extension. Please file the issue to the [Jupyter extension repository](https://github.com/microsoft/vscode-jupyter). Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our [issue reporting guidelines](https://aka.ms/vscodeissuereporting) for more information.\n\nHappy Coding!"
264
+
"comment": "It looks like this is caused by the Jupyter extension. Please file the issue to the [Jupyter extension repository](https://github.com/deepnote/vscode-deepnote). Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our [issue reporting guidelines](https://aka.ms/vscodeissuereporting) for more information.\n\nHappy Coding!"
-[ ] Ensure that any CI test failures have issues assigned to that area's owner.
5
5
-[ ] Work with the build champ to drive the build to green by fixing/disabling tests or pinging area owners to do so.
6
6
7
7
## Friday
8
-
-[ ] Review [Component Governance](https://dev.azure.com/monacotools/Monaco/_componentGovernance/191876) (Click on "microsoft/vscode-jupyter" on that page) and resolve all High/Severe issues.
8
+
-[ ] Review [Component Governance](https://dev.azure.com/monacotools/Monaco/_componentGovernance/191876) (Click on "deepnote/vscode-deepnote" on that page) and resolve all High/Severe issues.
9
9
-[ ] Focus on resolving `Critical` and `High` priority issues as others will be addressed in the `debt` week.
10
10
-[ ] Manually add any repository dependencies (if you can't add manually, refer [here](https://docs.opensource.microsoft.com/tools/cg/features/cgmanifest/)). Only add a cgmanifest.json if the components are not NPM or are not dev only.
11
-
Instructions on updating `npm` dependencies in `package.json` & `package-lock.json` can be found [here](https://github.com/microsoft/vscode-jupyter/wiki/Resolving-Component-Governance-and-Dependabot-issues-(updating-package-lock.json)).
11
+
Instructions on updating `npm` dependencies in `package.json` & `package-lock.json` can be found [here](https://github.com/deepnote/vscode-deepnote/wiki/Resolving-Component-Governance-and-Dependabot-issues-(updating-package-lock.json)).
12
12
-[ ] Create new release branch with format `release/release-YYYY.MM`.
13
13
* Note: The release branch is now ready for to be published (or hotfixed)
14
14
-[ ] Back on the `main` branch, bump the version in `package.json`.
[For contributing to the [Microsoft Python Language Server](https://github.com/Microsoft/python-language-server) see its own repo; for [Pylance](https://github.com/microsoft/pylance-release) see its own repo; for [debugpy](https://github.com/microsoft/debugpy) see its own repo]
At a high level we have a bunch of folders. Each high level is described in this wiki [page](https://github.com/microsoft/vscode-jupyter/wiki/Source-Code-Organization)
272
+
At a high level we have a bunch of folders. Each high level is described in this wiki [page](https://github.com/deepnote/vscode-deepnote/wiki/Source-Code-Organization)
273
273
274
274
### Typical workflow
275
275
@@ -282,16 +282,16 @@ Here's an example of a typical workflow:
282
282
1. Start VS code Insiders root
283
283
1. CTRL+SHIFT+B (run the task `compile`)
284
284
1. Make code changes
285
-
1. Write and [run](https://github.com/microsoft/vscode-jupyter/blob/29c4be79f64df1858692321b43c3079bb77bdd69/.vscode/launch.json#L252) unit tests if appropriate
286
-
1. Test with [`Extension`](https://github.com/microsoft/vscode-jupyter/blob/29c4be79f64df1858692321b43c3079bb77bdd69/.vscode/launch.json#L6) launch task
285
+
1. Write and [run](https://github.com/deepnote/vscode-deepnote/blob/29c4be79f64df1858692321b43c3079bb77bdd69/.vscode/launch.json#L252) unit tests if appropriate
286
+
1. Test with [`Extension`](https://github.com/deepnote/vscode-deepnote/blob/29c4be79f64df1858692321b43c3079bb77bdd69/.vscode/launch.json#L6) launch task
287
287
1. Repeat until works in normal extension
288
-
1. Test with [`Extension (web)`](https://github.com/microsoft/vscode-jupyter/blob/29c4be79f64df1858692321b43c3079bb77bdd69/.vscode/launch.json#L34) launch task
289
-
1. Run [jupyter notebook server](https://github.com/microsoft/vscode-jupyter/wiki/Connecting-to-a-remote-Jupyter-server-from-vscode.dev) to use in web testing
288
+
1. Test with [`Extension (web)`](https://github.com/deepnote/vscode-deepnote/blob/29c4be79f64df1858692321b43c3079bb77bdd69/.vscode/launch.json#L34) launch task
289
+
1. Run [jupyter notebook server](https://github.com/deepnote/vscode-deepnote/wiki/Connecting-to-a-remote-Jupyter-server-from-vscode.dev) to use in web testing
290
290
1. Repeat until works in web extension
291
-
1. Write integration tests and [run](https://github.com/microsoft/vscode-jupyter/blob/29c4be79f64df1858692321b43c3079bb77bdd69/.vscode/launch.json#L216) locally.
291
+
1. Write integration tests and [run](https://github.com/deepnote/vscode-deepnote/blob/29c4be79f64df1858692321b43c3079bb77bdd69/.vscode/launch.json#L216) locally.
292
292
1. Submit PR
293
293
1. Check PR output to make sure tests don't fail.
294
-
1. Debug [CI test failures](https://github.com/microsoft/vscode-jupyter/wiki/Tests)
294
+
1. Debug [CI test failures](https://github.com/deepnote/vscode-deepnote/wiki/Tests)
295
295
296
296
### Helping others
297
297
@@ -321,7 +321,7 @@ All development is actively done in the `main` branch of the
321
321
repository. This allows us to have a
322
322
[development build](#development-build) which is expected to be stable at
323
323
all times. Once we reach a release candidate, it becomes
0 commit comments